Process crash via unchecked Canon maker-note length
Published Apr 22, 2021 · Updated Aug 3, 2024
Heap-buffer over-read in Matthias Wandel Jhead 3.06 allows attackers to crash the command-line process with a crafted JPEG file. Canon maker-note parsing trusts the declared component count and calls Get16u past the allocated value buffer without first requiring enough bytes for the indexed field. Exploitation requires the crafted JPEG to be opened by Jhead; the demonstrated consequence is a process crash, and Debian reports no security impact beyond the CLI failure.
Summary
What happened
Heap-buffer over-read in Matthias Wandel Jhead 3.06 allows attackers to crash the command-line process with a crafted JPEG file. Canon maker-note parsing trusts the declared component count and calls Get16u past the allocated value buffer without first requiring enough bytes for the indexed field. Exploitation requires the crafted JPEG to be opened by Jhead; the demonstrated consequence is a process crash, and Debian reports no security impact beyond the CLI failure.
The record
- CVE
- CVE-2021-3496
- Published
- Apr 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Matthias Wandel
- Product
- Jhead
- Classifications
- CWE-787, CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=jhead 3.06.0.1
What conditions does exploitation require?
What is affected?
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
- 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