Local process crash via unterminated InkNames value
Published May 9, 2023 · Updated Jul 9, 2026
Heap-buffer over-read in the libtiff tiffcp utility 4.0.7 allows local users to crash the process with a malformed TIFF file. At tiffcp.c line 784, tiffcp passes an unterminated one-byte InkNames value to strlen, which reads beyond its heap allocation. Execution requires local access to run tiffcp on the crafted file; the demonstrated consequence is a process abort, not a library-wide write primitive.
Summary
What happened
Heap-buffer over-read in the libtiff tiffcp utility 4.0.7 allows local users to crash the process with a malformed TIFF file. At tiffcp.c line 784, tiffcp passes an unterminated one-byte InkNames value to strlen, which reads beyond its heap allocation. Execution requires local access to run tiffcp on the crafted file; the demonstrated consequence is a process abort, not a library-wide write primitive.
The record
- CVE
- CVE-2023-30086
- Published
- May 9, 2023
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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.
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
- tiffcp heap-buffer-overflow 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