Advisories for Npm/Safe-Eval package

All versions of the package safe-eval is vulnerable to Prototype Pollution via the safeEval function, due to improper sanitization of its parameter content.

All versions of the package safe-eval is vulnerable to Sandbox Bypass due to improper input sanitization. The vulnerability is derived from prototype pollution exploitation. Exploiting this vulnerability might result in remote code execution ("RCE"). Vulnerable functions: defineGetter, stack(), toLocaleString(), propertyIsEnumerable.call(), valueOf().

All versions of package safe-eval is vulnerable to Prototype Pollution which allows an attacker to add or modify properties of the Object.prototype.Consolidate when using the function safeEval. This is because the function uses vm variable, leading an attacker to modify properties of the Object.prototype.

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in safe-eval.

This affects all versions of package safe-eval. It is possible for an attacker to run an arbitrary command on the host machine.

By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.

By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.