{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36044 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36044 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36044 is a high-severity memory corruption vulnerability in rizinorg rizin, published on 6 Sep 2022. 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-2022-36044 and fix it if it is affected.\n\nWhat it is: CVE-2022-36044 is a high-severity memory corruption vulnerability in rizinorg rizin, published on 6 Sep 2022. 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-2022-36044 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-2022-36044/ (Markdown: https://insights.sbomify.com/CVE-2022-36044/index.md)","id":"CVE-2022-36044","markdown":"https://insights.sbomify.com/CVE-2022-36044/index.md","name":"CVE-2022-36044","record":{"aliases":["GHSA-mqcj-82c6-gh5q"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Reverse engineering framework","requires_auth":"none","summary":"An attacker can execute arbitrary code on a user's machine by tricking them into opening a malicious Luac file in Rizin.","user_interaction":"required","vuln_class":"memory_corruption"},"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-787","name":"Out-of-bounds Write"}],"description":"Rizin is a UNIX-like reverse engineering framework and command-line toolset. Versions 0.4.0 and prior are vulnerable to an out-of-bounds write when getting data from Luac files. A user opening a malicious Luac file could be affected by this vulnerability, allowing an attacker to execute code on the user's machine. Commits 07b43bc8aa1ffebd9b68d60624c9610cf7e460c7 and 05bbd147caccc60162d6fba9baaaf24befa281cd contain fixes for the issue.","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 Out-of-bounds Write vulnerability in Lua binary plugin","id":"CVE-2022-36044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Account takeover via cryptographically weak PRNG in NodeBB Forum","id":"CVE-2022-36045"},"packages":[],"prev":{"headline":"Rizin Double Free in bobj.c when using qnx binary plugin","id":"CVE-2022-36043"},"products":["rizin"],"published":"2022-09-06","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":"Rizin vulnerable to Integer Overflow in C++ demangler logic","id":"CVE-2023-40022","kev_date_added":null,"published":"2023-08-24"},{"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":"2025-04-23","vendors":["rizinorg"]},"summary":"An attacker can execute arbitrary code on a user's machine by tricking them into opening a malicious Luac file in Rizin.","url":"https://insights.sbomify.com/CVE-2022-36044/"}