Local code execution via EXIF heap overflow
Published Aug 27, 2024 · Updated Aug 28, 2024
Heap-buffer overflow in Eric Johnston exiftags 1.01 allows local users to execute arbitrary code by processing a crafted JPEG file. The parsetag function passes prop->value to strncpy, which reads 30 bytes beyond the allocated input region while parsing EXIF metadata. Exploitation requires the local utility to parse attacker-controlled JPEG data; the public artifact demonstrates a crash, and Debian disputes security impact.
Summary
What happened
Heap-buffer overflow in Eric Johnston exiftags 1.01 allows local users to execute arbitrary code by processing a crafted JPEG file. The parsetag function passes prop->value to strncpy, which reads 30 bytes beyond the allocated input region while parsing EXIF metadata. Exploitation requires the local utility to parse attacker-controlled JPEG data; the public artifact demonstrates a crash, and Debian disputes security impact.
The record
- CVE
- CVE-2024-42851
- Published
- Aug 27, 2024
- Updated
- Aug 28, 2024
- Vendor
- Eric Johnston
- Product
- exiftags
- Classifications
- CWE-787, CWE-122, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=1.01
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
- AddressSanitizer crash JPEG for exiftagsproof 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