- 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.
- Source
- cve@mitre.org
- NVD status
- Awaiting Analysis
CVSS 3.1
- Type
- Secondary
- Base score
- 5.3
- Impact score
- 1.4
- Exploitability score
- 3.9
- Vector string
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Severity
- MEDIUM
- 134c704f-9b21-4f2e-91b3-4a467353bcc0
- CWE-354
- Hype score
- Not currently trending
CVE-2024-56169 Validation Integrity Flaw in Fort Incomplete RPKI Data Risk: In Fort versions from 1.6.4 up to before 2.0.0, there's an issue with how it handles data checks. RPKI Relying Parties like Fort should ... https://t.co/8DKAb1tR1x
@VulmonFeeds
18 Dec 2024
37 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
CVE-2024-56169 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 rem… https://t.co/QLqVqcOVec
@CVEnew
18 Dec 2024
450 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes