Code execution via undersized JP2 box write
Published Apr 19, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Exiv2 before 0.27.4 allows attackers to execute code when a crafted image is processed for metadata writing. Jp2Image::doWriteMetadata trusts a JP2 box length below eight bytes and writes an eight-byte box header beyond the allocated heap buffer. Exploitation requires a victim to invoke a metadata-writing action, such as insert, on the crafted image; ordinary metadata reads do not trigger the flaw.
Summary
What happened
Heap-based buffer overflow in Exiv2 before 0.27.4 allows attackers to execute code when a crafted image is processed for metadata writing. Jp2Image::doWriteMetadata trusts a JP2 box length below eight bytes and writes an eight-byte box header beyond the allocated heap buffer. Exploitation requires a victim to invoke a metadata-writing action, such as insert, on the crafted image; ordinary metadata reads do not trigger the flaw.
The record
- CVE
- CVE-2021-29457
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Exiv2
- Product
- Exiv2
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 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
- Crafted JP2 metadata-write test caseproof 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