Description
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.
Remediation
References
https://github.com/patriksimek/vm2/commit/d9a7f3cc995d3d861e1380eafb886cb3c5e2b873#diff-b1a515a627d820118e76d0e323fe2f0589ed50a1eacb490f6c3278fe3698f164
https://github.com/patriksimek/vm2/issues/467
https://github.com/patriksimek/vm2/blob/master/lib/setup-sandbox.js#L71
https://github.com/patriksimek/vm2/security/advisories/GHSA-mrgp-mrhc-5jrq
https://www.oxeye.io/blog/vm2-sandbreak-vulnerability-cve-2022-36067
https://security.netapp.com/advisory/ntap-20221017-0002/
Related Vulnerabilities
CVE-2021-39235 Vulnerability in maven package org.apache.ozone:ozone-main
CVE-2021-29506 Vulnerability in maven package com.graphhopper:graphhopper-nav
CVE-2021-32808 Vulnerability in npm package ckeditor4
CVE-2020-28479 Vulnerability in npm package jointjs
CVE-2018-25031 Vulnerability in maven package org.webjars.npm:swagger-ui-dist