Skip to content

← Public intelligence

npm package

notevil

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratednpmAmendedPublished

    Sandbox Breakout / Prototype Pollution in notevil

    GHSA-9gxr-rhx6-4jgv

    Affected
    • npm notevil < 1.3.3
    Fixed in
    1.3.3· Vendor fix available
    Issue
    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 add the polluted property to Function. Recommendation Upgrade to version 1.3.3 or later.

    Recommended action: Upgrade to 1.3.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)osv.dev (2)Source checked Evidence →
  2. UnratednpmAmendedPublished

    Sandbox Breakout / Arbitrary Code Execution in notevil

    GHSA-7r5f-7qr4-pf6q

    Affected
    • npm notevil < 1.3.2
    Fixed in
    1.3.2· Vendor fix available
    Issue
    Versions of notevil prior to 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to prevent access to the Function constructor by not checking the return values of function calls. This allows attackers to access the Function prototype's constructor leading to the Sandbox Escape. An example payload is: Recommendation Upgrade to version 1.3.2 or later.

    Recommended action: Upgrade to 1.3.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →