Skip to content

← Public intelligence

npm package

json-ptr

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

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

  1. Medium, CVSS 5.6npmAmendedPublished

    Prototype Pollution in json-ptr

    CVE-2021-23509 · GHSA-8gwj-8hxc-285w

    Affected
    • npm json-ptr < 3.0.0
    Fixed in
    3.0.0· Vendor fix available
    Issue
    This affects the package json-ptr before 3.0.0. A type confusion vulnerability can lead to a bypass of CVE-2020-7766 when the user-provided keys used in the pointer parameter are arrays.

    Recommended action: Upgrade to 3.0.0 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. UnratednpmAmendedPublished

    Arbitrary Code Execution in json-ptr

    GHSA-rrqv-vjrw-hrcr

    Affected
    • npm json-ptr < 2.1.0
    Fixed in
    2.1.0· Vendor fix available
    Issue
    There is a security vulnerability in json-ptr versions prior to v2.1.0 in which an unscrupulous actor may execute arbitrary code. If your code sends un-sanitized user input to json-ptr's .get() method, your project is vulnerable to this injection-style vulnerability.

    Recommended action: Upgrade to 2.1.0 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 →
  3. High, CVSS 7.3npmAmendedPublished

    Arbitrary Code Execution in json-ptr

    CVE-2020-7766 · GHSA-x5r6-x823-9848

    Affected
    • npm json-ptr < 2.1.0
    Fixed in
    2.1.0· Vendor fix available
    Issue
    npm json-ptr before 2.1.0 has an arbitrary code execution vulnerability. The issue occurs in the set operation when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution.

    Recommended action: Upgrade to 2.1.0 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 →