{"vulnerability": "CVE-2024-56169", "sightings": [{"uuid": "a86682af-fa4c-4cb8-8e6d-9da6f202c006", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56169", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113671984999227241", "content": "", "creation_timestamp": "2024-12-18T04:40:41.937815Z"}, {"uuid": "045b4d34-3b70-46cb-bc12-deba607f8632", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56169", "type": "seen", "source": "https://t.me/cvedetector/13159", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56169 - Fort RPKI Invalid Route Origin Validation Data Cache\", \n  \"Content\": \"CVE ID : CVE-2024-56169 \nPublished : Dec. 18, 2024, 5:15 a.m. | 43\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-18T07:00:05.000000Z"}]}