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 4 September 2020.
- Which products and versions are affected?
- notevil (npm) SEMVER:introduced=0,fixed=1.3.3.
- Is there a fix for This vulnerability?
- Yes. notevil (npm): upgrade to 1.3.3 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.3 or later
npm install notevil@1.3.3
Technical details
The vulnerability is a sandbox escape leading to prototype pollution (CWE-1321) in notevil versions before 1.3.3. The package fails to properly restrict access to the main JavaScript context. An attacker can craft a malicious payload—such as try{a[b];}catch(e){e.constructor.constructor('return __proto__.arguments.callee.__proto__.polluted=true')()}—that leverages error handling and constructor chains to add or modify the Function prototype. This allows pollution of global object properties, affecting all code running in the same context. The attack requires the ability to pass untrusted code to notevil's evaluation function; no authentication is needed. The fix is available in version 1.3.3 and later.
Affected products
- notevil notevil <1.3.3
Timeline
- 2020-09-04: disclosed
- 2020-09-04: patched: Fix available in version 1.3.3 and later