Code execution via JPEG comment buffer over-read
Published Aug 11, 2023 · Updated Oct 9, 2024
Heap-buffer overflow in jhead 3.04 allows local users to execute arbitrary code or crash the process with a crafted JPEG comment. The process_COM function in jpgfile.c reads Data[a+1] after a carriage return without first ensuring that another byte remains in the allocated JPEG comment buffer. A local user must cause jhead to parse the crafted file; the demonstrated out-of-bounds read aborts the process, while the CVE record also reports code execution.
Summary
What happened
Heap-buffer overflow in jhead 3.04 allows local users to execute arbitrary code or crash the process with a crafted JPEG comment. The process_COM function in jpgfile.c reads Data[a+1] after a carriage return without first ensuring that another byte remains in the allocated JPEG comment buffer. A local user must cause jhead to parse the crafted file; the demonstrated out-of-bounds read aborts the process, while the CVE record also reports code execution.
The record
- CVE
- CVE-2020-28840
- Published
- Aug 11, 2023
- Updated
- Oct 9, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2023CVE publishedPublication date reported by the CVE source.
- Oct 9, 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.
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
- fuzzer&poc1.zip 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