# CVE-2017-16088: Sandbox Breakout in safe-eval

> Attackers can execute arbitrary code by accessing object constructors in the safe-eval Node.js module, bypassing its sandbox restrictions.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-ww6v-677g-p656

## What is CVE-2017-16088?

CVE-2017-16088 is a critical code injection vulnerability in HackerOne safe-eval node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The safe-eval module describes itself as a safer version of eval. By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

## Which versions are affected by CVE-2017-16088?

2 open source packages ship an affected version, including safe-eval. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `safe-eval` | npm | All versions to 0.3.0 | None |
| `safe-eval` | npm | All versions to 0.3.0 | None |

Products: Safe-Eval Project Safe-Eval.

## How do I fix CVE-2017-16088?

No fix has been published for CVE-2017-16088 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-16088 being exploited?

There is no known exploitation of CVE-2017-16088 in the wild and no public exploit code.

Public exploit code:

- Exploit CVE-2017-16088  (github_poc): https://github.com/Flyy-yu/CVE-2017-16088

## Other vulnerabilities in HackerOne safe-eval node module

- [CVE-2023-26122](https://insights.sbomify.com/CVE-2023-26122/): safe-eval vulnerable to Sandbox Bypass due to improper input sanitization (high 8.8)
- [CVE-2020-7710](https://insights.sbomify.com/CVE-2020-7710/): Sandbox Escape (high 8.1)
- [CVE-2023-26121](https://insights.sbomify.com/CVE-2023-26121/): safe-eval vulnerable to Prototype Pollution via the safeEval function (high 7.5)
- [CVE-2022-25904](https://insights.sbomify.com/CVE-2022-25904/): Prototype Pollution (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16088 and fix it if it is affected.

What it is: CVE-2017-16088 is a critical code injection vulnerability in HackerOne safe-eval node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16088 in the wild and no public exploit code.

Affected packages and fixed versions:
- safe-eval (npm): affected all versions up to 0.3.0; no fix listed
- safe-eval (npm): affected all versions up to 0.3.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/CVE-2017-16088/ (Markdown: https://insights.sbomify.com/CVE-2017-16088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16088
- OSV: https://osv.dev/vulnerability/CVE-2017-16088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16088/
Summaries are generated and may contain mistakes; the official description above is the record.