First published: Wed Dec 18 2024(Updated: )
A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI manifests are listings of relevant files that clients are supposed to verify. Assuming everything else is correct, the most recent version of a manifest should be prioritized over other versions, to prevent replays, accidental or otherwise. Manifests contain the manifestNumber and thisUpdate fields, which can be used to gauge the relevance of a given manifest, when compared to other manifests. The former is a serial-like sequential number, and the latter is the date on which the manifest was created. However, the product does not compare the up-to-dateness of the most recently fetched manifest against the cached manifest. As such, it's prone to a rollback to a previous version if it's served a valid outdated manifest. This leads to outdated route origin validation.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiGate | <2.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-56170 is classified as a medium severity vulnerability due to its impact on validation integrity within RPKI manifests.
To address CVE-2024-56170, upgrade Fort software to version 2.0.0 or later, which includes the necessary fixes.
CVE-2024-56170 affects Fort software versions prior to 2.0.0, specifically with version 1.6.4 and earlier.
Yes, CVE-2024-56170 can potentially enable replay attacks due to inadequate validation integrity of RPKI manifests.
An RPKI manifest lists relevant files that are intended to be verified by clients, making the integrity validation crucial to prevent issues such as replays.