CVE-2023-29199
Vm2 Project Vm2 ≤ 3.9.16
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-29199 is a critical-severity Improper Control of Dynamically-Managed Code Resources (CWE-913) vulnerability in Vm2 Project Vm2. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 10% 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.
The vulnerability is present in the source code transformer exception sanitization logic of the vm2 JavaScript sandbox library in versions up to 3.9.15. It stems from a flaw that permits bypass of the handleException() routine, resulting in leakage of unsanitized host exceptions that can be leveraged to break out of the sandbox. The issue is tracked under CWE-913 and carries a CVSS 3.1 score of 9.8.
An unauthenticated remote attacker can supply crafted input to a vm2-protected application and exploit the exception handling weakness to escape the sandbox, ultimately executing arbitrary code with the privileges of the host process. This grants full host-level remote code execution without requiring user interaction or prior credentials.
The maintainers addressed the issue in vm2 release 3.9.16 via a targeted commit that strengthens exception sanitization. Security advisories and the associated GitHub issue recommend immediate upgrade to the patched version; the fix is also documented in the project’s security advisory GHSA-xj72-wvfv-8985.
The EPSS probability reached a peak of 0.3136 before receding to its current value of 0.2497, indicating moderate ongoing exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1428
Vulnerability Data
There exists a vulnerability in source code transformer (exception sanitization logic) of vm2 for versions up to 3.9.15, allowing attackers to bypass `handleException()` and leak unsanitized host exceptions which can be used to escape the sandbox and run arbitrary code…
more
in host context. A threat actor can bypass the 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.16` of `vm2`.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
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 (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.
A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing, developer training and capability) that reach improper control of dynamic code resources when they manifest as injection, insecure deserialization or logic flaws in first-party code; this stops exploitation for that slice but leaves a bounded remainder (e.g. third-party libraries, runtime configuration, or outsourced development that evades the org's rules)
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.
Security testing can detect dynamic code weaknesses but does not prevent them at design or coding time.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-913, a class-level weakness, and none of its children carries one either.