{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-56169 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-56169 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-56169 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-56169 and fix it if it is affected.\n\nWhat it is: CVE-2024-56169 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-56169 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-56169/ (Markdown: https://insights.sbomify.com/CVE-2024-56169/index.md)","id":"CVE-2024-56169","markdown":"https://insights.sbomify.com/CVE-2024-56169/index.md","name":"CVE-2024-56169","record":{"aliases":["DEBIAN-CVE-2024-56169","GHSA-pggg-fp6x-7ww3","UBUNTU-CVE-2024-56169"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RPKI validation software","requires_auth":"none","summary":"Fort fails to use cached RPKI data as a fallback during fetch errors, leading to incomplete route origin validation and potential security bypass.","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:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"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.","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-56169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2024-56170"},"packages":[],"prev":{"headline":"Security feature bypass in AMD EPYC™ 7001 Series","id":"CVE-2024-56161"},"products":["n/a"],"published":"2024-12-18","related":[{"cvss_score":7.5,"headline":"Integer overflow in fort-validator","id":"CVE-2024-56375","kev_date_added":null,"published":"2024-12-22"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-45235","kev_date_added":null,"published":"2024-08-24"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-45238","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-10","vendors":["n/a"]},"summary":"Fort fails to use cached RPKI data as a fallback during fetch errors, leading to incomplete route origin validation and potential security bypass.","url":"https://insights.sbomify.com/CVE-2024-56169/"}