Description
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.
Remediation
References
https://github.com/patriksimek/vm2/issues/515
https://github.com/patriksimek/vm2/commit/d534e5785f38307b70d3aac1945260a261a94d50
https://gist.github.com/seongil-wi/2a44e082001b959bfe304b62121fb76d
https://github.com/patriksimek/vm2/security/advisories/GHSA-7jxr-cg7f-gpgv
Related Vulnerabilities
CVE-2019-11002 Vulnerability in maven package org.webjars.npm:materialize-css
CVE-2017-11341 Vulnerability in npm package node-sass
CVE-2023-30843 Vulnerability in npm package payload
CVE-2021-28165 Vulnerability in maven package org.eclipse.jetty:jetty-io
CVE-2023-48088 Vulnerability in maven package com.xuxueli:xxl-job-admin