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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://nicmx.github.io/FORT-validator/CVE.html |
|
History
Mon, 14 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Tue, 22 Apr 2025 16:00:00 +0000
| 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 |
Thu, 26 Dec 2024 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-346 | |
| 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 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. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published: 2024-12-18T00:00:00
Updated: 2024-12-26T19:07:44.267Z
Reserved: 2024-12-18T00:00:00
Link: CVE-2024-56170
Updated: 2024-12-26T18:56:40.780Z
Status : Analyzed
Published: 2024-12-18T05:15:09.093
Modified: 2025-04-22T15:35:05.487
Link: CVE-2024-56170
No data.