@locker/near-membrane-base is vulnerable to Sandbox Escape
87
High Risk
@locker/near-membrane-base implements the near-membrane boundary that isolates sandboxed code from the host realm. Sandboxed code can define an accessor property on a live target, which plants the sandbox-authored getter or setter directly on the raw host-shared object, so a later read from the host realm executes sandbox code with the raw object as receiver and exposes host-only state. Sandboxed code can also install an inherited numeric-index setter on Array.prototype so that the membrane's argument marshalling, which populates a plain array with [[Set]], invokes that setter and overwrites the marshalled foreign target pointer to redirect cross-boundary calls. Both flaws let untrusted sandboxed code escape the membrane and read or corrupt state in the host realm. The fix scopes accessor descriptors to the inert shadow target and marshals arguments with [[DefineOwnProperty]] instead of [[Set]].
You are affected if you are using a version that falls within the vulnerable range and you rely on the membrane to isolate untrusted code that executes inside the sandbox.
@locker/near-membrane-base is vulnerable to Sandbox Escape in versions 0.7.0 - 0.18.0.
Upgrade the @locker/near-membrane-base 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.