Process crash via unchecked Canon EXIF offset
Published Mar 23, 2022 · Updated Aug 3, 2024
Out-of-bounds read in jhead 3.04 and 3.05 allows attackers to crash the command-line process via a crafted Canon EXIF JPEG. The ProcessCanonMakerNoteDir function adds a maker-note byte count to an unchecked 32-bit offset, producing a pointer outside the EXIF buffer. The file must reach a workflow that invokes jhead; the consequence is limited to termination of that jhead process.
Summary
What happened
Out-of-bounds read in jhead 3.04 and 3.05 allows attackers to crash the command-line process via a crafted Canon EXIF JPEG. The ProcessCanonMakerNoteDir function adds a maker-note byte count to an unchecked 32-bit offset, producing a pointer outside the EXIF buffer. The file must reach a workflow that invokes jhead; the consequence is limited to termination of that jhead process.
The record
- CVE
- CVE-2021-28276
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1203
- Attack vector
- network
- 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
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