{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-40022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-40022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-40022 is a high-severity vulnerability in rizinorg rizin, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-40022 and fix it if it is affected.\n\nWhat it is: CVE-2023-40022 is a high-severity vulnerability in rizinorg rizin, published on 24 Aug 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-40022 in the wild and no public exploit code.\n\nAffected product: rizinorg rizin. 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-2023-40022/ (Markdown: https://insights.sbomify.com/CVE-2023-40022/index.md)","id":"CVE-2023-40022","markdown":"https://insights.sbomify.com/CVE-2023-40022/index.md","name":"CVE-2023-40022","record":{"aliases":["GHSA-92h6-wwc2-53cq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Reverse engineering framework","requires_auth":"none","summary":"An integer overflow in the C++ demangler allows attackers to cause a denial of service via crafted binaries.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rizin","vendor":"rizin"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Rizin is a UNIX-like reverse engineering framework and command-line toolset. Versions 0.6.0 and prior are vulnerable to integer overflow in `consume_count` of `src/gnu_v2/cplus-dem.c`. The overflow check is valid logic but, is missing the modulus if the block once compiled. The compiler sees this block as unreachable code since the prior statement is multiplication by 10 and fails to consider overflow assuming the count will always be a multiple of 10. Rizin version 0.6.1 contains a fix for the issue. A temporary workaround would be disabling C++ demangling using the configuration option `bin.demangle=false`.","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":"Rizin vulnerable to Integer Overflow in C++ demangler logic","id":"CVE-2023-40022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"Yaklang Plugin's Fuzztag Component Allows Unauthorized Local File Reading","id":"CVE-2023-40023"},"packages":[],"prev":{"headline":"Timing Attack Reveals CSRF Tokens in oppia","id":"CVE-2023-40021"},"products":["rizin"],"published":"2023-08-24","related":[{"cvss_score":9.1,"headline":"rizin before v0.6.3 is vulnerable to Improper Neutralization of Special Elements via meta_set function in librz/analysis/meta.","id":"CVE-2024-31668","kev_date_added":null,"published":"2024-12-17"},{"cvss_score":7.8,"headline":"Memory corruption in rizin","id":"CVE-2021-3674","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":7.8,"headline":"Rizin has stack-based buffer overflow when parsing GDB registers profile files","id":"CVE-2023-27590","kev_date_added":null,"published":"2023-03-14"},{"cvss_score":7.8,"headline":"Out-of-bounds write when parsing DEX files in Rizin","id":"CVE-2022-36039","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.8,"headline":"Rizin Out-of-bounds Write vulnerability in pyc/marshal.c","id":"CVE-2022-36040","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":7.8,"headline":"Rizin Out-of-bounds Write vulnerability in Mach-O binary plugin","id":"CVE-2022-36041","kev_date_added":null,"published":"2022-09-06"}],"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":"total"},"state":"PUBLISHED","updated":"2024-10-02","vendors":["rizinorg"]},"summary":"An integer overflow in the C++ demangler allows attackers to cause a denial of service via crafted binaries.","url":"https://insights.sbomify.com/CVE-2023-40022/"}