Browse / AI Framework and Platform Flaws / Sandbox escape
Sandbox escape
76 records in AI Framework and Platform Flaws.
- vm2: Mutable Proxies for Host Intrinsic Prototypes Allows Sandbox Escape Mutable proxies to host prototypes let sandboxed JavaScript write to shared host intrinsics and break out of the VM.
- vm2's Transformer Fast-Path Bypass Exposes Internal State Variable A regex fast path skips AST checks for code without certain keywords, letting sandboxed code reach an internal state object with privileged functions.
- VM2 Has a Sandbox Escape Issue via SuppressedError Errors thrown from deferred DisposableStack callbacks expose a host-realm constructor through SuppressedError, letting code leave the vm2 sandbox.
- VM2 Has a WASM Sandbox Escape A host-realm TypeError surfaces unsanitised through WebAssembly exception handling, giving attacker code a constructor chain to the host process.
- VM2 Has Sandbox Breakout Through Promise Species A previous sandbox fix can be undone by overwriting built-ins used in its reset logic, letting sandboxed code reach the host process.
- VM2 Has Sandbox Breakout Through Inspect Function Access through vm2's inspect path reaches the host sandbox object, letting attacker code escape the sandbox and run host commands.
- VM2 Sandbox Breakout Through __lookupGetter__ A getter lookup inside vm2 returns host-side objects, letting sandboxed code reach the host Function constructor and run commands outside the sandbox.
- n8n has a Python Task Runner Sandbox Escape Vulnerability An authenticated workflow author can break out of the Python task runner sandbox used by a Code node and run commands on the runner container.
- n8n has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode The AlaSQL sandbox behind the Merge node's SQL mode fails to block certain statements, letting an authenticated workflow editor read host files and run code.
- n8n has a Sandbox Escape in its JavaScript Task Runner A workflow author can break out of the JavaScript task runner sandbox and execute code on the host outside its boundary.
- n8n has Arbitrary File Read via Python Code Node Sandbox Escape The Python Code node sandbox fails to restrict certain built-in objects, letting a workflow author read host files or execute code outside the sandbox.
- n8n has a Python sandbox escape An authenticated user can break out of the Python code node sandbox when task runners are enabled, running code outside the intended boundary.
- vm2 has a Sandbox Escape A promise callback in the sandbox is sanitised for one Promise realm but not the host-global one, letting sandboxed code reach host process objects.
- Self-hosted n8n has Legacy Code node that enables arbitrary file read/write In legacy Code node mode, internal helper functions remain reachable from workflow scripts, letting editors read and write host files outside the intended restrictions.
- vm2 Sandbox Escape vulnerability A flaw in how vm2 sanitizes Promise handlers lets code running inside the sandbox reach the host and execute arbitrary code.
- vm2 Sandbox Escape vulnerability A custom inspect function lets code inside the vm2 sandbox break out and run arbitrary Node.js code on the host.
- vm2 vulnerable to Inspect Manipulation Code running inside the vm2 sandbox can obtain a writable reference to the inspect function and change console.log options, breaking isolation.
- vm2 Sandbox Escape vulnerability Unexpected creation of a host object through Proxy handling lets sandboxed code escape vm2 and run code on the host.
- vm2 Sandbox Escape vulnerability Sandboxed code triggers an unsanitised host exception inside the exception handler, gaining host-realm objects that it can use to run arbitrary code.
- vm2 Sandbox Escape vulnerability Exception sanitisation in the vm2 source transformer can be skipped, so raw host exception objects leak and let sandboxed code reach the host context.
- vm2 vulnerable to sandbox escape Host objects passed to Error.prepareStackTrace for unhandled async errors leak out of the vm2 sandbox, letting untrusted code run on the host.
- vm2 vulnerable to Arbitrary Code Execution A WeakMap prototype lookup in vm2 gives sandboxed code access to a host object, allowing it to escape the sandbox.
- vm2 vulnerable to Sandbox Escape resulting in Remote Code Execution on host Crafted JavaScript breaks out of the vm2 sandbox and runs code with the host's privileges.
- vm2 before 3.6.11 vulnerable to sandbox escape Infinite recursion triggers a host-side RangeError whose returned object exposes the host mainModule, allowing the sandboxed code to spawn child processes.
- Sandbox bypass in vm2 Host error objects leak through stack trace generation, letting sandboxed code reach host internals and run arbitrary code.
- Prototype Pollution in vm2 Prototype pollution inside vm2 lets sandboxed code escape its boundary and run arbitrary code on the host.