{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-31949 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-31949 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-31949 and fix it if it is affected.\n\nWhat it is: CVE-2024-31949 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-31949 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-31949/ (Markdown: https://insights.sbomify.com/CVE-2024-31949/index.md)","id":"CVE-2024-31949","markdown":"https://insights.sbomify.com/CVE-2024-31949/index.md","name":"CVE-2024-31949","record":{"aliases":["DEBIAN-CVE-2024-31949","GHSA-f3q5-vrp5-crqj"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FRRouting network stack","requires_auth":"none","summary":"An attacker can cause a denial of service in FRRouting by sending malformed MP/GR capability data, triggering an infinite loop.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"frrouting","vendor":"frrouting"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"In FRRouting (FRR) through 9.1, an infinite loop can occur when receiving a MP/GR capability as a dynamic capability because malformed data results in a pointer not advancing.","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-31949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-31950"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2024-31948"},"products":["n/a"],"published":"2024-04-07","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2024-44070","kev_date_added":null,"published":"2024-08-19"},{"cvss_score":9.8,"headline":"bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a \"flowspec overflow.\"","id":"CVE-2023-38406","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.1,"headline":"Use after free in n/a","id":"CVE-2022-37035","kev_date_added":null,"published":"2022-08-02"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26127","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26128","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26129","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2026-37457","kev_date_added":null,"published":"2026-05-01"}],"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-04","vendors":["n/a"]},"summary":"An attacker can cause a denial of service in FRRouting by sending malformed MP/GR capability data, triggering an infinite loop.","url":"https://insights.sbomify.com/CVE-2024-31949/"}