Application hang via crafted XLSX parsing
Published Jul 19, 2021 · Updated Aug 3, 2024
Uncontrolled resource consumption in SheetJS and SheetJS Pro through 0.16.9 allows attackers to exhaust CPU via a crafted .xlsx document. Public disclosures identify xlsx.js as the parsing locus but do not disclose the malformed workbook structure or the specific unbounded operation. A user or application must read the attacker-supplied workbook; successful processing hangs the application at full CPU utilization.
Summary
What happened
Uncontrolled resource consumption in SheetJS and SheetJS Pro through 0.16.9 allows attackers to exhaust CPU via a crafted .xlsx document. Public disclosures identify xlsx.js as the parsing locus but do not disclose the malformed workbook structure or the specific unbounded operation. A user or application must read the attacker-supplied workbook; successful processing hangs the application at full CPU utilization.
The record
- CVE
- CVE-2021-32014
- Published
- Jul 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo