Skip to content

← Public intelligence

npm package

jointjs

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 jointjs

    CVE-2021-23444 · GHSA-f3pp-32qc-36w4

    Affected
    • npm jointjs < 3.4.2
    Fixed in
    3.4.2· Vendor fix available
    Issue
    This affects the package jointjs before 3.4.2. A type confusion vulnerability can lead to a bypass of CVE-2020-28480 when the user-provided keys used in the path parameter are arrays in the setByPath function.

    Recommended action: Upgrade to 3.4.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 →
  2. High, CVSS 7.5npmAmendedPublished

    Denial of Service (DoS) via the unsetByPath function in jsjoints

    CVE-2020-28479 · GHSA-cq8r-fc3q-6hg2

    Affected
    • npm jointjs < 3.3.0
    Fixed in
    3.3.0· Vendor fix available
    Issue
    The package jointjs before 3.3.0 are vulnerable to Denial of Service (DoS) via the unsetByPath function.

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

    Prototype pollution in JointJS

    CVE-2020-28480 · GHSA-qwp9-52h8-xgg8

    Affected
    • npm jointjs < 3.3.0
    Fixed in
    3.3.0· Vendor fix available
    Issue
    The package jointjs before 3.3.0 are vulnerable to Prototype Pollution via util.setByPath (https://resources.jointjs.com/docs/jointjs/v3.2/joint.htmlutil.setByPath). The path used the access the object's key and set the value is not properly sanitized, leading to a Prototype Pollution.

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