patriksimek · vm2
The vm2 sandbox library from patriksimek fails to properly handle host objects passed to Error.prepareStackTrace when unhandled async errors occur, in versions prior to 3.9.15. An attacker who can get untrusted code run inside the sandbox can bypass its protections and execute code on the host, requiring no privileges or user interaction and reachable over the network.
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 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.
Public exploit code (PoC-in-GitHub) appeared 1 day after disclosure. No confirmed exploitation is recorded.
7 fixes in vm2 over 15 months. The latest fix listed for vm2 is 3.9.18.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
1 package in 1 ecosystem. Main package: vm2.
Upgrade to 3.9.17 or later
Fixes this CVE and 1 other known vulnerability in this package (CVE-2023-30547).
npm install vm2@3.9.17First fixed in 3.9.15 for CVE-2023-29017.
| If you run | Upgrade to |
|---|---|
| All versions before 3.9.15 | 3.9.17first fix for this CVE: 3.9.15 |
“Up to” means the second version is the fix and is not affected.