Description (CNA)
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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| patriksimek / vm2 | affected 0 before 3.11.7; unaffected 3.11.7 |
CWE
CWE-269
References
- https://github.com/patriksimek/vm2/security/advisories/GHSA-8686-vhfx-7r3j
- https://www.vulncheck.com/advisories/vm2-before-3.11.7-authentication-bypass-via-node-prefix
ADP enrichment
No English description supplied.