{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-56375 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-56375 is a high-severity vulnerability in nicmx fort-validator, published on 22 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-56375 and fix it if it is affected.\n\nWhat it is: CVE-2024-56375 is a high-severity vulnerability in nicmx fort-validator, published on 22 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-56375 in the wild and no public exploit code.\n\nAffected product: nicmx fort-validator. 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-56375/ (Markdown: https://insights.sbomify.com/CVE-2024-56375/index.md)","id":"CVE-2024-56375","markdown":"https://insights.sbomify.com/CVE-2024-56375/index.md","name":"CVE-2024-56375","record":{"aliases":["DEBIAN-CVE-2024-56375","GHSA-533g-7w58-g89m"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"RPKI validator","requires_auth":"none","summary":"A malicious RPKI repository can cause a crash in Fort validator via an integer underflow leading to an infinite loop and out-of-bounds access.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"An integer underflow was discovered in Fort 1.6.3 and 1.6.4 before 1.6.5. A malicious RPKI repository that descends from a (trusted) Trust Anchor can serve (via rsync or RRDP) a Manifest RPKI object containing an empty fileList. Fort dereferences (and, shortly afterwards, writes to) this array during a shuffle attempt, before the validation that would normally reject it when empty. This out-of-bounds access is caused by an integer underflow that causes the surrounding loop to iterate infinitely. Because the product is permanently stuck attempting to overshuffle an array that doesn't actually exist, a crash is nearly guaranteed.","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":"Integer overflow in fort-validator","id":"CVE-2024-56375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in REDCap","id":"CVE-2024-56376"},"packages":[],"prev":{"headline":"Django has a potential denial-of-service vulnerability in IPv6 validation","id":"CVE-2024-56374"},"products":["fort-validator"],"published":"2024-12-22","related":[{"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"},{"cvss_score":5.3,"headline":"Other in n/a","id":"CVE-2024-56169","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["nicmx"]},"summary":"A malicious RPKI repository can cause a crash in Fort validator via an integer underflow leading to an infinite loop and out-of-bounds access.","url":"https://insights.sbomify.com/CVE-2024-56375/"}