Memory corruption via integer-overflowed tile allocation
Published Jan 28, 2020 · Updated Aug 4, 2024
Heap-based buffer overflow in OpenJPEG 2.3.1 allows remote attackers to corrupt memory via a crafted JPEG 2000 image. An integer overflow in opj_tcd_init_tile miscalculates tile-component storage, so opj_t1_clbl_decode_processor writes decoded coefficients beyond the undersized heap allocation. A consuming application must process attacker-controlled image content; the demonstrated result is a crash, while the out-of-bounds write also corrupts process memory.
Summary
What happened
Heap-based buffer overflow in OpenJPEG 2.3.1 allows remote attackers to corrupt memory via a crafted JPEG 2000 image. An integer overflow in opj_tcd_init_tile miscalculates tile-component storage, so opj_t1_clbl_decode_processor writes decoded coefficients beyond the undersized heap allocation. A consuming application must process attacker-controlled image content; the demonstrated result is a crash, while the out-of-bounds write also corrupts process memory.
The record
- CVE
- CVE-2020-8112
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Crafted JPEG 2000 crashing 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