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.
Metrics
Affected Vendors & Products
References
History
Mon, 10 Feb 2025 23:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-354 | |
Metrics |
cvssV3_1
|
Wed, 18 Dec 2024 04:45:00 +0000
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 |
|

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2025-02-10T22:14:44.765Z
Reserved: 2024-12-18T00:00:00.000Z
Link: CVE-2024-56169

Updated: 2024-12-20T21:02:27.132Z

Status : Awaiting Analysis
Published: 2024-12-18T05:15:08.853
Modified: 2025-02-10T23:15:15.203
Link: CVE-2024-56169

No data.