CVE-2024-56169
First published: Wed Dec 18 2024(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Fortinet FortiGate | <2.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-56169?
CVE-2024-56169 has been classified with a significant severity level due to the integrity issue that affects RPKI data validation.
How do I fix CVE-2024-56169?
To mitigate CVE-2024-56169, upgrade to Fort 2.0.0 or later, where the integrity validation issue is resolved.
Who is affected by CVE-2024-56169?
CVE-2024-56169 affects users of Fort versions prior to 2.0.0 that utilize RPKI data.
What type of issue is CVE-2024-56169?
CVE-2024-56169 is identified as a validation integrity issue in RPKI data handling.
What product does CVE-2024-56169 relate to?
CVE-2024-56169 relates specifically to the Fort software developed by Fortinet.
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/event
- vendor/fort
- canonical/fortinet fortigate