Description (CNA)
vm2 before 3.11.8 does not fully enforce the allowAsync: false option in VM and NodeVM. While localPromise.prototype.then is replaced with a handler that throws 'Async not available', the sandbox's Promise static methods (Promise.resolve, Promise.all, Promise.race, Promise.any, and Promise.allSettled) still assimilate attacker-supplied thenables: native promise resolution performs PromiseResolveThenableJob and invokes the sandboxed code's then method in a microtask without passing through the patched then, so the async restriction is never applied. As a result, sandboxed script can schedule work that runs after VM.run() or NodeVM.run() has returned and outside the configured timeout, continuing to execute after the host believes execution is complete.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| patriksimek / vm2 | affected 0 before 3.11.8; unaffected 3.11.8 |
CWE
CWE-693
References
- https://github.com/patriksimek/vm2/security/advisories/GHSA-f8gf-w286-fmq2
- https://www.vulncheck.com/advisories/vm2-before-3.11.8-allowasync-bypass-via-promise-thenable
ADP enrichment
No English description supplied.