Application crash via out-of-bounds format-byte read
Published Aug 15, 2023 · Updated Oct 8, 2024
Heap buffer over-read in libxls 1.6.2 allows remote attackers to crash applications that process a crafted XLS file. The get_string function in src/xlstool.c reads the string-format flag one byte beyond a four-byte heap allocation while parsing a STYLE record. Exploitation requires an application to parse attacker-supplied XLS content; the published proof demonstrates an AddressSanitizer abort, not code execution.
Summary
What happened
Heap buffer over-read in libxls 1.6.2 allows remote attackers to crash applications that process a crafted XLS file. The get_string function in src/xlstool.c reads the string-format flag one byte beyond a four-byte heap allocation while parsing a STYLE record. Exploitation requires an application to parse attacker-supplied XLS content; the published proof demonstrates an AddressSanitizer abort, not code execution.
The record
- CVE
- CVE-2023-38856
- Published
- Aug 15, 2023
- Updated
- Oct 8, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2023CVE publishedPublication date reported by the CVE source.
- Oct 8, 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.
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.
Public exploit references
- libxls get_string fuzzer crash inputproof 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