Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 3 September 2020.
- Which products and versions are affected?
- notevil (npm) SEMVER:introduced=0,fixed=1.3.2.
- Is there a fix for This vulnerability?
- Yes. notevil (npm): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run notevil (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- notevil (npm): upgrade to 1.3.2 or later
npm install notevil@1.3.2
Technical details
The vulnerability is a sandbox escape caused by inadequate filtering of object prototype chain access. The library fails to validate return values of function calls, allowing attackers to traverse the prototype chain via Object.getOwnPropertyDescriptors() to access the Function constructor. Once obtained, the Function constructor can be invoked to execute arbitrary JavaScript code with full system access. The attack requires no authentication and operates on the input string passed to the safeEval function. The vulnerability was patched in version 1.3.2.
Affected products
- notevil notevil before 1.3.2
Timeline
- 2020-09-03: disclosed
- 2020-09-03: patched: version 1.3.2 released