Memory corruption via overflowing string-count allocation
Published Jun 2, 2025 · Updated Nov 3, 2025
Integer overflow in the Shared String Table parser in xls2csv 0.95 allows attackers to corrupt memory through a malformed Excel file. The parse_sst function multiplies the untrusted cstUnique string count by pointer size in a 32-bit allocation, then writes string pointers beyond the undersized heap array. Local processing of the crafted workbook can corrupt the utility's process memory and crash it without authentication or additional user interaction.
Summary
What happened
Integer overflow in the Shared String Table parser in xls2csv 0.95 allows attackers to corrupt memory through a malformed Excel file. The parse_sst function multiplies the untrusted cstUnique string count by pointer size in a 32-bit allocation, then writes string pointers beyond the undersized heap array. Local processing of the crafted workbook can corrupt the utility's process memory and crash it without authentication or additional user interaction.
The record
- CVE
- CVE-2024-48877
- Published
- Jun 2, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-680, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Talos malformed Excel file proof of conceptproof of concept · demonstrated
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