How severe is GHSA-9gxr-rhx6-4jgv?

No CVSS score has been assigned to GHSA-9gxr-rhx6-4jgv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9gxr-rhx6-4jgv?

GHSA-9gxr-rhx6-4jgv affects the following packages: notevil (npm). Ecosystems affected: npm.

How do I fix GHSA-9gxr-rhx6-4jgv?

Update notevil to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9gxr-rhx6-4jgv is resolved across your whole dependency graph.

How do I detect GHSA-9gxr-rhx6-4jgv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for notevil, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9gxr-rhx6-4jgv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-9gxr-rhx6-4jgv actively exploited in the wild?

No public exploit code has been indexed for GHSA-9gxr-rhx6-4jgv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9gxr-rhx6-4jgv published, and has it been updated?

GHSA-9gxr-rhx6-4jgv was published on September 4, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Sandbox Breakout / Prototype Pollution in notevilGHSA-9gxr-rhx6-4jgv

GHSA-9gxr-rhx6-4jgv is a security vulnerability in notevil. A fix is available for notevil — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

notevilnpm

19Kdownloads / week

Description

Versions of notevil prior to 1.3.3 are vulnerable to Sandbox Escape leading to Prototype pollution. The package fails to restrict access to the main context, allowing attacker to add or modify an object's prototype.

Evaluating the payload try{a[b];}catch(e){e.constructor.constructor('return __proto__.arguments.callee.__proto__.polluted=true')()} add the polluted property to Function.

Recommendation

Upgrade to version 1.3.3 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`notevil`	all versions	1.3.3`npm install notevil@1.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for notevil, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update notevil to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9gxr-rhx6-4jgv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `notevil` prior to 1.3.3 are vulnerable to Sandbox Escape leading to Prototype pollution. The package fails to restrict access to the main context, allowing attacker to add or modify an object's prototype. Evaluating the payload ```try{a[b];}catch(e){e.constructor.constructor('return __proto__.arguments.callee.__proto__.polluted=true')()}``` add the `polluted` property to Function. ## Recommendation Upgrade to version 1.3.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9gxr-rhx6-4jgv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works