{"answers":{"affected":"2 open source packages ship an affected version, including vm2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-37466 in the wild and no public exploit code.","fix":"Upgrade vm2 to 3.10.0 or later.","what":"CVE-2023-37466 is a critical code injection vulnerability in patriksimek vm2, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-37466 and fix it if it is affected.\n\nWhat it is: CVE-2023-37466 is a critical code injection vulnerability in patriksimek vm2, published on 13 Jul 2023. 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-2023-37466 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.10.0\n- vm2 (npm): affected all versions; fixed in 3.10.0\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-37466/ (Markdown: https://insights.sbomify.com/CVE-2023-37466/index.md)","id":"CVE-2023-37466","markdown":"https://insights.sbomify.com/CVE-2023-37466/index.md","name":"CVE-2023-37466","record":{"aliases":["GHSA-cchq-frgv-rjh5","ROOT-APP-NPM-CVE-2023-37466"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Attackers can bypass sandbox restrictions to execute arbitrary code within the vm2 Node.js library environment.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vm2","vendor":"vm2_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"vm2 is an advanced vm/sandbox for Node.js. The library contains critical security issues and should not be used for production. The maintenance of the project has been discontinued. In vm2 for versions up to 3.9.19, `Promise` handler sanitization can be bypassed with the `@@species` accessor property allowing attackers to escape the sandbox and run arbitrary code, potentially allowing remote code execution inside the context of vm2 sandbox. Version 3.10.0 contains a patch for the issue.","ecosystems":["npm"],"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":"vm2 Sandbox Escape vulnerability","id":"CVE-2023-37466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Discourse CSP nonce reuse vulnerability for anonymous users","id":"CVE-2023-37467"},"packages":[{"ecosystem":"npm","fixed":["3.10.0"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-cchq-frgv-rjh5"},{"ecosystem":"npm","fixed":["3.10.0"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-cchq-frgv-rjh5"}],"prev":{"headline":"Incorrect Authentication Tag length usage in AES GCM decryption in OpenIDC/cjose","id":"CVE-2023-37464"},"products":["vm2"],"published":"2023-07-13","related":[{"cvss_score":10,"headline":"vm2: Sandbox Escape","id":"CVE-2026-43997","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2: Sandbox escape","id":"CVE-2026-44005","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2: Sandbox Escape","id":"CVE-2026-44006","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2 Sandbox Escape vulnerability","id":"CVE-2023-29017","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":10,"headline":"vm2 vulnerable to Sandbox Escape before v3.9.11","id":"CVE-2022-36067","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":9.9,"headline":"vm2: NodeVM builtin allowlist bypass via `module` builtin's `Module._load` allows sandbox escape","id":"CVE-2026-43999","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":9.8,"headline":"vm2: Snabox breakout via `neutralizeArraySpeciesBatch`","id":"CVE-2026-44008","kev_date_added":null,"published":"2026-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"total"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["patriksimek"]},"summary":"Attackers can bypass sandbox restrictions to execute arbitrary code within the vm2 Node.js library environment.","url":"https://insights.sbomify.com/CVE-2023-37466/"}