{"uuid": "2ddab9c0-ed68-4f53-bc3a-1a7e4a298473", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-45236", "type": "seen", "source": "https://t.me/cvedetector/4068", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-45236 - Fort RPKI Relying Party Crash Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-45236 \nPublished : Aug. 24, 2024, 11:15 p.m. | 22\u00a0minutes ago \nDescription : An issue was discovered in Fort before 1.6.3. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) a signed object containing an empty signedAttributes field. Fort accesses the set's elements without sanitizing it first. Because Fort is an RPKI Relying Party, a crash can lead to Route Origin Validation unavailability, which can lead to compromised routing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-25T01:44:47.000000Z"}