Process crash via unchecked EXIF value pointer
Published Mar 23, 2022 · Updated Aug 3, 2024
Out-of-bounds read in jhead 3.04 and 3.05 allows context-dependent attackers to crash the program via a crafted JPEG file. ProcessExifDir accepts a crafted EXIF value offset that makes PrintFormatNumber pass an out-of-range pointer to Get16u, which dereferences it. A victim must process the attacker-supplied JPEG; the demonstrated consequence is a process crash, not code execution or data modification.
Summary
What happened
Out-of-bounds read in jhead 3.04 and 3.05 allows context-dependent attackers to crash the program via a crafted JPEG file. ProcessExifDir accepts a crafted EXIF value offset that makes PrintFormatNumber pass an out-of-range pointer to Get16u, which dereferences it. A victim must process the attacker-supplied JPEG; the demonstrated consequence is a process crash, not code execution or data modification.
The record
- CVE
- CVE-2021-28275
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-704, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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
- jhead-multi-seg crafted JPEG 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