vm2 is vulnerable to Out-of-bounds Write
100
Critical Risk
A host allocated Buffer passed into the sandbox (a builtin return such as zlib.deflateSync, an embedder supplied buffer, or a callback argument) exposes Node's shared 64 KiB pool through .buffer and the legacy .parent accessors. Sandbox code can open a full width view of the backing ArrayBuffer to read past its own data and overwrite unrelated host buffers. The bridge used backing store ownership only for sandbox allocated buffers, not for host views that crossed into the sandbox. The fix limits every host ArrayBufferView at the bridge by identity, returns a bounded copy when a view does not own its whole store, and blocks the raw backing store getters.
You are affected if you are using a version that falls within the vulnerable range and you pass pool backed Buffer values from a host builtin or callback (for example an allowlisted zlib) into sandboxed code.
vm2 is vulnerable to Out-of-bounds Write in versions 0.1.0 - 3.12.1.
Upgrade the vm2 library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.