Skip to content

← Public intelligence

npm package

safer-eval

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. Critical, CVSS 9.9npmAmendedPublished

    Sandbox Breakout / Arbitrary Code Execution in safer-eval

    CVE-2019-10759 · GHSA-r3x4-wr4h-pw33

    Affected
    • npm safer-eval < 1.3.4
    Fixed in
    1.3.4· Vendor fix available
    Issue
    Versions of safer-eval prior to 1.3.4 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. For example, evaluating he string console.constructor.constructor('return process')().env prints process.env to the console. Recommendation Upgrade to version 1.3.4 or later.

    Recommended action: Upgrade to 1.3.4 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 →
  2. Critical, CVSS 9.9npmAmendedPublished

    Sandbox Breakout / Arbitrary Code Execution in safer-eval

    CVE-2019-10760 · GHSA-hgch-jjmr-gp7w

    Affected
    • npm safer-eval < 1.3.2
    Fixed in
    1.3.2· Vendor fix available
    Issue
    Versions of safer-eval before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code. Recommendation Upgrade to version 1.3.2.

    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 →