Skip to content

← Public intelligence

npm package

xlsx

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.5npmAmendedPublished

    Denial of Service in SheetJS Pro

    CVE-2021-32012 · GHSA-3x9f-74h4-2fqr

    Affected
    • npm xlsx < 0.17.0
    Fixed in
    0.17.0· Vendor fix available
    Issue
    SheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 1 of 2).

    Recommended action: Upgrade to 0.17.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. Medium, CVSS 5.5npmAmendedPublished

    Denial of Service in SheetsJS Pro

    CVE-2021-32013 · GHSA-8vcr-vxm8-293m

    Affected
    • npm xlsx < 0.17.0
    Fixed in
    0.17.0· Vendor fix available
    Issue
    SheetJS Pro through 0.16.9 allows attackers to cause a denial of service (memory consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js (issue 2 of 2).

    Recommended action: Upgrade to 0.17.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. Medium, CVSS 5.5npmAmendedPublished

    Denial of Service in SheetJS Pro

    CVE-2021-32014 · GHSA-g973-978j-2c3p

    Affected
    • npm xlsx < 0.17.0
    Fixed in
    0.17.0· Vendor fix available
    Issue
    SheetJS Pro through 0.16.9 allows attackers to cause a denial of service (CPU consumption) via a crafted .xlsx document that is mishandled when read by xlsx.js.

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