{"id":"CVE-2024-56169","aliases":["DEBIAN-CVE-2024-56169","EUVD-2024-52993","GHSA-pggg-fp6x-7ww3","UBUNTU-CVE-2024-56169"],"status":"published","title":"A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying...","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.","severity":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-11","score":0.00185,"percentile":0.08225,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-354"],"published":"2024-12-18T00:00:00Z","modified":"2026-11-02T12:03:02Z","affected":[{"source":"osv","ecosystem":"Debian:12","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.5.4-1","1.5.4-1+deb12u1","1.6.1-1","1.6.1-1~bpo12+2","1.6.2-1","1.6.3-1","1.6.3-1~bpo12+1","1.6.4+20240930-1","1.6.4+20240930-1~bpo12+1","1.6.5-1","1.6.6-1","1.6.6-1~bpo12+1","1.6.7-1","1.6.7-1~bpo13+1","1.6.8-1","1.7.0.experimental-1"]},{"source":"osv","ecosystem":"Debian:13","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.6-1","1.6.7-1","1.6.7-1~bpo13+1","1.6.8-0+deb13u1","1.6.8-1","1.7.0.experimental-1"]},{"source":"osv","ecosystem":"Debian:14","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.6-1","1.6.7-1","1.6.7-1~bpo13+1","1.6.8-1","1.7.0.experimental-1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.1.1-2","1.1.2-1","1.1.3-1","1.2.0-1","1.2.0-1ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.5.1-1","1.5.2-1","1.5.3-1","1.5.3-1build1","1.5.3-1ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.5.4-1","1.6.1-1","1.6.1-1build2","1.6.1-1build3","1.6.1-1ubuntu0.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.6-1","1.6.6-1build1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.7-1","1.6.8-1","1.7.0.experimental-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"fort-validator","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.6-1build1","1.6.7-1"]}],"products":[{"vendor":"nicmx","product":"fort_validator"}],"references":[{"url":"https://nicmx.github.io/FORT-validator/CVE.html","tags":["Vendor Advisory","web","report"]},{"url":"https://github.com/NICMx/FORT-validator/issues/82","tags":["Issue Tracking","Vendor Advisory","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56169","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-pggg-fp6x-7ww3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56169.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2024-56169","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-56169","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-56169","tags":["report"]}],"sources":{"cve":[{"id":"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.","status":"published","published":"2024-12-18T00:00:00Z","modified":"2025-02-10T22:14:44.765Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"adp"}],"cwes":["CWE-354"],"updated_at":"2026-11-02T14:33:57.638551Z"}],"euvd":[{"id":"EUVD-2024-52993","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.","status":"published","published":"2024-12-18T00:00:00Z","modified":"2025-02-10T22:14:44Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-03T00:04:00.770319Z"}],"ghsa":[{"id":"GHSA-pggg-fp6x-7ww3","title":"A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying...","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.","status":"published","published":"2024-12-18T06:30:49Z","modified":"2025-02-11T00:31:47Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"cwes":["CWE-354"],"updated_at":"2026-11-02T14:59:51.679807Z"}],"nvd":[{"id":"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.","status":"published","published":"2024-12-18T05:15:08.853Z","modified":"2026-06-17T08:11:46.453Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-354"],"updated_at":"2026-11-02T14:10:40.507978Z"}],"osv":[{"id":"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.","status":"published","published":"2024-12-18T00:00:00Z","modified":"2026-10-28T02:30:22.966803793Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:44.777182Z"},{"id":"DEBIAN-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.","status":"published","published":"2024-12-18T05:15:08.853Z","modified":"2026-11-02T12:03:02.633462445Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:44.429177Z"},{"id":"UBUNTU-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.","status":"published","published":"2024-12-18T05:15:00Z","modified":"2026-10-17T12:56:40.41327971Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T16:55:15.331356Z"}]}}