Service crash via NULL cell-string dereference
Published Feb 23, 2021 · Updated Aug 4, 2024
NULL pointer dereference in xls2csv before 1.6.2 allows context-dependent attackers to crash the process with a crafted XLS file. At src/xls2csv.c line 199, formula-cell handling passes a NULL cell->str value to strcmp without first checking the pointer. Exploitation requires the crafted file to be processed by xls2csv and terminates that converter process, with no reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in xls2csv before 1.6.2 allows context-dependent attackers to crash the process with a crafted XLS file. At src/xls2csv.c line 199, formula-cell handling passes a NULL cell->str value to strcmp without first checking the pointer. Exploitation requires the crafted file to be processed by xls2csv and terminates that converter process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2020-27819
- Published
- Feb 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Libxls Project
- Product
- libxls
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libxls before 1.6.2
What conditions does exploitation require?
What is affected?
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
- Crafted XLS crash 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