{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1240 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-1240 is a high-severity memory corruption vulnerability in Radare Radare2, published on 6 Apr 2022. 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-2022-1240 and fix it if it is affected.\n\nWhat it is: CVE-2022-1240 is a high-severity memory corruption vulnerability in Radare Radare2, published on 6 Apr 2022. 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-2022-1240 in the wild and no public exploit code.\n\nAffected product: Radare Radare2. 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-2022-1240/ (Markdown: https://insights.sbomify.com/CVE-2022-1240/index.md)","id":"CVE-2022-1240","markdown":"https://insights.sbomify.com/CVE-2022-1240/index.md","name":"CVE-2022-1240","record":{"aliases":["GHSA-m6g3-mrp2-c625","UBUNTU-CVE-2022-1240"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"radare2 reverse engineering tool","requires_auth":"none","summary":"A heap buffer overflow in radare2 allows attackers to execute arbitrary code or cause a denial of service via crafted Mach-O binaries.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"radare2","vendor":"radare"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Heap buffer overflow in libr/bin/format/mach0/mach0.c in GitHub repository radareorg/radare2 prior to 5.8.6. If address sanitizer is disabled during the compiling, the program should executes into the `r_str_ncpy` function. Therefore I think it is very likely to be exploitable. For more general description of heap buffer overflow, see [CWE](https://cwe.mitre.org/data/definitions/122.html).","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":"Heap buffer overflow in libr/bin/format/mach0/mach0.c in radareorg/radare2","id":"CVE-2022-1240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"radare:radare2","products":["radare:radare2"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Ask Me \u003c 6.8.2 - Reflected Cross-Site Scripting","id":"CVE-2022-1241"},"packages":[],"prev":{"headline":"HubSpot \u003c 8.8.15 - Contributor+ Blind SSRF","id":"CVE-2022-1239"},"products":["radareorg/radare2"],"published":"2022-04-06","related":[{"cvss_score":10,"headline":"Buffer Overflow and Potential Code Execution in Radare2","id":"CVE-2025-1864","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":10,"headline":"Out-of-bounds Write in radare2","id":"CVE-2025-1744","kev_date_added":null,"published":"2025-02-28"},{"cvss_score":10,"headline":"Denial of service in radare2","id":"CVE-2021-32494","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":10,"headline":"Use after free in radare2","id":"CVE-2021-32495","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29646","kev_date_added":null,"published":"2024-12-17"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46569","kev_date_added":null,"published":"2023-10-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46570","kev_date_added":null,"published":"2023-10-28"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["radareorg"]},"summary":"A heap buffer overflow in radare2 allows attackers to execute arbitrary code or cause a denial of service via crafted Mach-O binaries.","url":"https://insights.sbomify.com/CVE-2022-1240/"}