Application crash via unchecked anonymous-field allocation failure
Published Aug 8, 2024 · Updated Jan 23, 2026
Null pointer dereference in libtiff on affected Red Hat Enterprise Linux releases allows local users to crash TIFF-processing applications. When allocation fails, _TIFFCreateAnonField returns NULL and tif_dirread.c passes that pointer to _TIFFMergeFields, which dereferences it in tif_dirinfo.c without validation. Exploitation requires local control of memory pressure or fault injection, and the bounded consequence is termination of the calling application.
Summary
What happened
Null pointer dereference in libtiff on affected Red Hat Enterprise Linux releases allows local users to crash TIFF-processing applications. When allocation fails, _TIFFCreateAnonField returns NULL and tif_dirread.c passes that pointer to _TIFFMergeFields, which dereferences it in tif_dirinfo.c without validation. Exploitation requires local control of memory pressure or fault injection, and the bounded consequence is termination of the calling application.
The record
- CVE
- CVE-2024-7006
- Published
- Aug 8, 2024
- Updated
- Jan 23, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Jan 23, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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