{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45234 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-45234 is a high-severity denial of service vulnerability in n/a, published on 24 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45234 and fix it if it is affected.\n\nWhat it is: CVE-2024-45234 is a high-severity denial of service vulnerability in n/a, published on 24 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45234 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-45234/ (Markdown: https://insights.sbomify.com/CVE-2024-45234/index.md)","id":"CVE-2024-45234","markdown":"https://insights.sbomify.com/CVE-2024-45234/index.md","name":"CVE-2024-45234","record":{"aliases":["DEBIAN-CVE-2024-45234","GHSA-h6q6-xxwv-mm6v","UBUNTU-CVE-2024-45234"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RPKI relying party library","requires_auth":"none","summary":"A malicious RPKI repository can cause a panic in Fort, leading to Route Origin Validation unavailability and potential routing compromise.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fort-validator","vendor":"nicmx"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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) an ROA or a Manifest containing a signedAttrs encoded in non-canonical form. This bypasses Fort's BER decoder, reaching a point in the code that panics when faced with data not encoded in DER. Because Fort is an RPKI Relying Party, a panic can lead to Route Origin Validation unavailability, which can lead to compromised routing.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of service in n/a","id":"CVE-2024-45234","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2024-45235"},"packages":[],"prev":{"headline":"Powermail TYPO3 extension Broken Access Control in the OutputController","id":"CVE-2024-45233"},"products":["n/a"],"published":"2024-08-24","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45237","kev_date_added":null,"published":"2024-08-24"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-45236","kev_date_added":null,"published":"2024-08-24"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-45239","kev_date_added":null,"published":"2024-08-24"},{"cvss_score":5.3,"headline":"Other in n/a","id":"CVE-2024-56170","kev_date_added":null,"published":"2024-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["n/a"]},"summary":"A malicious RPKI repository can cause a panic in Fort, leading to Route Origin Validation unavailability and potential routing compromise.","url":"https://insights.sbomify.com/CVE-2024-45234/"}