Sandbox Breakout in safe-eval
Affected versions of `safe-eval` are vulnerable to a sandbox escape. By accessing object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox. ## Proof of Concept: This code accesses the process object and calls `.exit()` ```js var safeEval = require('safe-eval'); safeEval("this.constructor.constructor('return process')().exit()"); ``` ## Recommendation Update to version 0.4.0 or later
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-16088US | critical10.0 | Exploit | ||
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 effective… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-ww6v-677g-p656ADVISORY
- https://github.com/hacksparrow/safe-eval/issues/5WEB
- https://github.com/hacksparrow/safe-eval/pull/13WEB
- https://github.com/patriksimek/vm2/issues/59WEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-16088ADVISORY
- https://www.npmjs.com/advisories/337WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan