vm2 Sandbox Escape vulnerability
Published 12 Apr 2023 · Updated 8 Nov 2023
Affected package
- Affected
- <3.9.16
- Fixed in
- 3.9.16
npm install vm2@3.9.16Details
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 in host context.
Impact
A threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox.
Patches
This vulnerability was patched in the release of version 3.9.16 of vm2.
Workarounds
None.
References
Github Issue - https://github.com/patriksimek/vm2/issues/516 PoC - https://gist.github.com/leesh3288/f05730165799bf56d70391f3d9ea187c
For more information
If you have any questions or comments about this advisory:
- Open an issue in VM2
Thanks to Xion (SeungHyun Lee) of KAIST Hacking Lab for disclosing this vulnerability.
Is GHSA-xj72-wvfv-8985 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vm2, and gives you the command that fixes it.
References
- Linkgithub.com/patriksimek/vm2/security/advisories/GHSA-xj72-wvfv-8985
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-29199
- Linkgithub.com/patriksimek/vm2/issues/516
- Linkgithub.com/patriksimek/vm2/commit/24c724daa7c09f003e556d7cd1c7a8381cb985d7
- Linkgist.github.com/leesh3288/f05730165799bf56d70391f3d9ea187c
- Packagegithub.com/patriksimek/vm2
- Linkgithub.com/patriksimek/vm2/releases/tag/3.9.16
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.