CVE-2024-56169

Published Dec 18, 2024 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-52993 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.
History
Type Values Removed Values Added
Metrics epss

{'score': 0.00024}

epss

{'score': 0.00026}

Type Values Removed Values Added
First Time appeared Nicmx
Nicmx fort Validator
CPEs cpe:2.3:a:nicmx:fort_validator:*:*:*:*:*:*:*:*
Vendors & Products Nicmx
Nicmx fort Validator
Type Values Removed Values Added
Weaknesses CWE-354
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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
Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Feb 10, 2025, 10:14 PM
Reserved
Dec 18, 2024, 12:00 AM
Status
Analyzed
Published
Dec 18, 2024, 5:15 AM
Modified
Jun 17, 2026, 8:11 AM