Application crash via malformed ColorMap copy
Published Sep 9, 2021 · Updated Aug 4, 2024
Heap buffer overflow in LibTIFF 4.0.10 allows attackers to crash image-processing applications through a crafted TIFF file. While tiffcp copies the file's ColorMap tag, _TIFFVSetField allocates a 32-byte array that TIFFWriteDirectoryTagColormap later reads as 131,072 bytes. A user or automated workflow must make tiffcp process the file; the demonstrated result is an out-of-bounds read and process termination.
Summary
What happened
Heap buffer overflow in LibTIFF 4.0.10 allows attackers to crash image-processing applications through a crafted TIFF file. While tiffcp copies the file's ColorMap tag, _TIFFVSetField allocates a 32-byte array that TIFFWriteDirectoryTagColormap later reads as 131,072 bytes. A user or automated workflow must make tiffcp process the file; the demonstrated result is an out-of-bounds read and process termination.
The record
- CVE
- CVE-2020-19144
- Published
- Sep 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 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?
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
- LibTIFF issue 159 proof-of-concept TIFFproof 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