Process crash via oversized section-array memmove
Published Mar 23, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in jhead 3.04 and 3.05 allows attackers to crash the process by supplying a crafted JPEG file. RemoveUnknownSections in jpgfile.c miscalculates the memmove length by one Section_t entry after freeing an unknown section, reading past the heap allocation while compacting the section array. A user must run jhead with the -purejpg option against the malicious image; the demonstrated consequence is an AddressSanitizer-detected abort.
Summary
What happened
Heap-based buffer overflow in jhead 3.04 and 3.05 allows attackers to crash the process by supplying a crafted JPEG file. RemoveUnknownSections in jpgfile.c miscalculates the memmove length by one Section_t entry after freeing an unknown section, reading past the heap allocation while compacting the section array. A user must run jhead with the -purejpg option against the malicious image; the demonstrated consequence is an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2021-28277
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, 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.
Public exploit references
- tests_61787.jpg crashing 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