Heap overflow via unchecked JP2 box lengths
Published Apr 30, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Exiv2 before 0.27.4 allows attackers to gain code execution via a crafted image during metadata writing. Jp2Image::encodeJp2Header() trusted JP2 box and sub-box lengths while copying data into a heap buffer without sufficient bounds checks. Exploitation requires a victim to run Exiv2 with a write operation such as insert; ordinary metadata reading does not trigger the flaw.
Summary
What happened
Heap-based buffer overflow in Exiv2 before 0.27.4 allows attackers to gain code execution via a crafted image during metadata writing. Jp2Image::encodeJp2Header() trusted JP2 box and sub-box lengths while copying data into a heap buffer without sufficient bounds checks. Exploitation requires a victim to run Exiv2 with a write operation such as insert; ordinary metadata reading does not trigger the flaw.
The record
- CVE
- CVE-2021-29464
- Published
- Apr 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Exiv2
- Product
- Exiv2
- Classifications
- CWE-122, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 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=< 0.27.4
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
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