vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, 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.11 of vm2. There are no known workarounds.
References
Link | Resource |
---|---|
https://github.com/patriksimek/vm2/commit/d9a7f3cc995d3d861e1380eafb886cb3c5e2b873#diff-b1a515a627d820118e76d0e323fe2f0589ed50a1eacb490f6c3278fe3698f164 | Patch Third Party Advisory |
https://github.com/patriksimek/vm2/issues/467 | Issue Tracking Third Party Advisory |
https://github.com/patriksimek/vm2/blob/master/lib/setup-sandbox.js#L71 | Exploit Third Party Advisory |
https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq | Patch Third Party Advisory |
https://www.oxeye.io/blog/vm2-sandbreak-vulnerability-cve-2022-36067 | Exploit Third Party Advisory |
https://security.netapp.com/advisory/ntap-20221017-0002/ | Third Party Advisory |
Configurations
Information
Published : 2022-09-06 15:15
Updated : 2022-11-07 19:03
NVD link : CVE-2022-36067
Mitre link : CVE-2022-36067
JSON object : View
CWE
CWE-913
Improper Control of Dynamically-Managed Code Resources
Products Affected
vm2_project
- vm2