We release patches for security vulnerabilities. Which versions are eligible receiving such patches depend on the CVSS v3.0 Rating:
| Version | Supported |
|---|---|
| 1.7.x | ✅ |
| 1.6.x | ✅ |
| 1.5.x | ❌ |
| < 1.5 | ❌ |
Please report security vulnerabilities to kryptobaseddev@gmail.com.
Please include:
- A description of the vulnerability
- Steps to reproduce the issue
- Possible impact of the vulnerability
- Suggested fix (if any)
We will acknowledge receipt within 48 hours and provide a more detailed response within 7 days indicating the next steps in handling your report.
After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
When using Ferrous Forge:
- Keep your Rust toolchain updated — Use
ferrous-forge rust updateregularly - Run security audits — Enable the safety pipeline to run
cargo audit - Review bypasses — Regularly check
ferrous-forge safety auditfor unexpected bypasses - Validate templates — When fetching templates from external sources, validate them first
Ferrous Forge includes several security-focused features:
- Dependency Scanning: Integration with
cargo auditfor vulnerability detection - Unsafe Code Prevention:
unsafe_code = "forbid"enforced by default - Lock File Validation: Ensures dependencies haven't been tampered with
- Audit Logging: All bypasses and critical configuration changes are logged
When we receive a security bug report, we will:
- Confirm the problem and determine the affected versions
- Audit code to find any similar problems
- Prepare fixes for all supported versions
- Release new versions as quickly as possible
- Publicly disclose the issue after all supported versions have been patched
If you have suggestions on how this process could be improved, please submit a pull request or open an issue to discuss.