CVE-2023-29017
Vm2 Project Vm2 ≤ 3.9.15
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2023-29017 is a critical-severity Improper Control of Dynamically-Managed Code Resources (CWE-913) vulnerability in Vm2 Project Vm2. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
vm2 is a JavaScript sandbox used to execute untrusted code while restricting access to a whitelist of Node.js built-in modules. The vulnerability, tracked as CVE-2023-29017, affects all versions prior to 3.9.15 and stems from improper handling of host objects passed to Error.prepareStackTrace during unhandled asynchronous errors. This flaw is assigned CWE-913 and carries a CVSS 3.1 base score of 10.0, reflecting its critical severity.
An attacker able to supply code to the sandbox can trigger the mishandling condition to escape the vm2 isolation boundary, obtaining arbitrary code execution on the underlying host system. Exploitation requires no authentication or user interaction and can be performed over the network, making any application that embeds an affected vm2 instance directly exposed.
The issue was resolved in vm2 3.9.15 by a commit that corrects the stack-trace handling path. The accompanying GitHub Security Advisory and issue tracker entries state there are no known workarounds, so the only mitigation is to upgrade to the patched release.
EPSS for the CVE reached a peak of 0.7944 and currently stands at 0.7496 after receding, indicating sustained and material interest in exploitation following disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1229
Vulnerability Data
vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Prior to version 3.9.15, vm2 was not properly handling host objects passed to `Error.prepareStackTrace` in case of unhandled async errors. A threat actor could bypass the…
more
sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.15 of vm2. There are no known workarounds.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring explicit authorization and ongoing control of mobile code implements proper management of dynamically loaded code resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly include controls that prevent improper handling of dynamic code resources.
Blocking unauthorized code execution directly limits the ability to abuse dynamically-managed resources.
Runtime-environment monitoring can detect exploitation of the weakness but does not prevent it.
Vulnerability identification can surface instances of CWE-913 but does not mitigate the root weakness.
Hardened configuration baselines can restrict dynamic code execution and variable access at runtime.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect dynamic code weaknesses but does not prevent them at design or coding time.
Secure development lifecycle mandates controls on dynamic code generation and resource management.
Application security requirements explicitly address restrictions on dynamic code execution and resource access.
Secure architecture principles require design controls that prevent improper dynamic code resource manipulation.
Secure coding standards directly prohibit unsafe dynamic code resource handling and injection patterns.
Environment separation reduces exposure of dynamic code resources but does not address the underlying weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913
Windows 11 (1 rule)
- V-253283 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913