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.
Loading...
Loading...
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2018-07-18. NVD baseline CVSS 10.0; sources differ by 0.0.
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.
June 7, 2018
November 21, 2024
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| npm | safe-eval | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| safe-eval | — | — | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16088
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.
npm:safe-eval
CWE-610