{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-56170 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-56170 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-56170 is a medium-severity vulnerability in n/a, published on 18 Dec 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-56170 and fix it if it is affected.\n\nWhat it is: CVE-2024-56170 is a medium-severity vulnerability in n/a, published on 18 Dec 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-56170 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-56170/ (Markdown: https://insights.sbomify.com/CVE-2024-56170/index.md)","id":"CVE-2024-56170","markdown":"https://insights.sbomify.com/CVE-2024-56170/index.md","name":"CVE-2024-56170","record":{"aliases":["DEBIAN-CVE-2024-56170","GHSA-hjvf-q4w6-qv8p","UBUNTU-CVE-2024-56170"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RPKI validation library","requires_auth":"none","summary":"An attacker can bypass RPKI route origin validation by serving outdated manifests, leading to potential route hijacking or incorrect routing decisions.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fort-validator","vendor":"nicmx"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI manifests are listings of relevant files that clients are supposed to verify. Assuming everything else is correct, the most recent version of a manifest should be prioritized over other versions, to prevent replays, accidental or otherwise. Manifests contain the manifestNumber and thisUpdate fields, which can be used to gauge the relevance of a given manifest, when compared to other manifests. The former is a serial-like sequential number, and the latter is the date on which the manifest was created. However, the product does not compare the up-to-dateness of the most recently fetched manifest against the cached manifest. As such, it's prone to a rollback to a previous version if it's served a valid outdated manifest. This leads to outdated route origin validation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2024-56170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in libxml2","id":"CVE-2024-56171"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2024-56169"},"products":["n/a"],"published":"2024-12-18","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-45234","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"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-26","vendors":["n/a"]},"summary":"An attacker can bypass RPKI route origin validation by serving outdated manifests, leading to potential route hijacking or incorrect routing decisions.","url":"https://insights.sbomify.com/CVE-2024-56170/"}