Application crash via repeated malformed LZW strip decoding
Published May 17, 2023 · Updated Jan 22, 2025
NULL pointer dereference in LibTIFF 4.5.0 allows local users to crash TIFF-processing applications with a crafted LZW-compressed TIFF file. LZWDecode retries a strip missing an end-of-information marker after an earlier decode error, leaving codep NULL before reading codep->value. Processing the crafted file is required; the demonstrated consequence is an application crash, not data disclosure or modification.
Summary
What happened
NULL pointer dereference in LibTIFF 4.5.0 allows local users to crash TIFF-processing applications with a crafted LZW-compressed TIFF file. LZWDecode retries a strip missing an end-of-information marker after an earlier decode error, leaving codep NULL before reading codep->value. Processing the crafted file is required; the demonstrated consequence is an application crash, not data disclosure or modification.
The record
- CVE
- CVE-2023-2731
- Published
- May 17, 2023
- Updated
- Jan 22, 2025
- Vendor
- LibTIFF
- Product
- LibTIFF
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2023CVE publishedPublication date reported by the CVE source.
- Jan 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in libtiff v4.5.0
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
- LibTIFF issue 548 poc_fileproof 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