A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.
References
| Link | Resource |
|---|---|
| https://github.com/NICMx/FORT-validator/issues/82 | Issue Tracking Vendor Advisory |
| https://nicmx.github.io/FORT-validator/CVE.html | Vendor Advisory |
Configurations
History
No history.
Information
Published : 2024-12-18 05:15
Updated : 2025-04-22 16:24
NVD link : CVE-2024-56169
Mitre link : CVE-2024-56169
CVE.ORG link : CVE-2024-56169
JSON object : View
Products Affected
nicmx
- fort_validator
CWE
CWE-354
Improper Validation of Integrity Check Value
