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.
References
Link | Resource |
---|---|
https://gist.github.com/seongil-wi/2a44e082001b959bfe304b62121fb76d | Exploit |
https://github.com/patriksimek/vm2/commit/d534e5785f38307b70d3aac1945260a261a94d50 | Patch |
https://github.com/patriksimek/vm2/issues/515 | Exploit Issue Tracking |
https://github.com/patriksimek/vm2/security/advisories/GHSA-7jxr-cg7f-gpgv | Vendor Advisory |
Configurations
History
No history.
Information
Published : 2023-04-06 20:15
Updated : 2024-02-28 20:13
NVD link : CVE-2023-29017
Mitre link : CVE-2023-29017
CVE.ORG link : CVE-2023-29017
JSON object : View
Products Affected
vm2_project
- vm2
CWE
CWE-913
Improper Control of Dynamically-Managed Code Resources