CyberRota Analysis
AI-GeneratedThe vm2 library versions prior to 3.11.7 are vulnerable due to improper handling of `node:`-prefixed built-in specifiers in negative wildcard entries within NodeVM's require policy. This flaw allows untrusted sandboxed code to bypass restrictions and access the host's `child_process` module, potentially enabling arbitrary command execution on the host system. Organizations using vm2 for sandboxing untrusted code should prioritize upgrading to version 3.11.7 to mitigate this critical vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
vm2 through 3.11.6 does not normalize `node:`-prefixed builtin specifiers when evaluating user-supplied negative (deny) entries in a NodeVM wildcard require policy. Although NodeVM strips the `node:` prefix during require() resolution, negative wildcard entries are matched by exact string comparison against the canonical builtin names, so a policy such as `new NodeVM({ require: { builtin: ['*', '-node:child_process'] } })` fails to deny the canonical `child_process` module. Sandboxed code can therefore obtain the host `child_process` builtin via `require('child_process')` or `require('node:child_process')`, gaining references to process-spawning APIs such as execSync and spawn, which is equivalent to host command-execution capability for untrusted sandbox code. Fixed in vm2 3.11.7.