Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2021-32013

MEDIUM

CVE-2021-32013 is a medium-severity (CVSS 5.5) Uncontrolled Resource Consumption vulnerability in org.webjars.npm:xlsx. O3 Security confirms whether CVE-2021-32013 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in SheetsJS Pro

Published
Jul 22, 2021
Updated
Feb 17, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Feb 17, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
xlsxnpm
12.5Mdownloads / week

Description

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).

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:xlsxall versions0.17.0
📦npmxlsxall versions0.17.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:xlsx. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.webjars.npm:xlsx to 0.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32013 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-32013 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-32013. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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).
O3 Security · Impact-Aware SCA

Is CVE-2021-32013 in your dependencies?

O3 detects CVE-2021-32013 across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2021-32013: Denial of Service in… | O3 Security