| Name | CVE-2024-56169 |
| 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 (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 1090916 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| fort-validator (PTS) | bullseye | 1.5.3-1~deb11u1 | vulnerable |
| bullseye (security) | 1.5.3-1~deb11u2 | vulnerable |
| bookworm | 1.5.4-1+deb12u1 | vulnerable |
| trixie | 1.6.6-1 | vulnerable |
| forky, sid | 1.6.7-1 | vulnerable |
The information below is based on the following data on fixed versions.
Notes
[trixie] - fort-validator <postponed> (Minor issue, revisit when fixed upstream)
[bookworm] - fort-validator <postponed> (Minor issue, revisit when fixed upstream)
[bullseye] - fort-validator <postponed> (Minor issue, wait until it's fixed upstream)
https://github.com/NICMx/FORT-validator/issues/82