Decompressor crash via stale image pointer destruction
Published Jun 29, 2020 · Updated Aug 4, 2024
Use-after-free in OpenJPEG 2.3.1 and earlier allows attackers to crash opj_decompress via a mixed directory of valid and invalid images. In src/bin/jp2/opj_decompress.c, image and stream pointers persist across loop iterations, allowing an error path to destroy an image that a preceding iteration freed. Exploitation requires directory mode to process a mix of valid and invalid images; the supported consequence is abnormal process termination.
Summary
What happened
Use-after-free in OpenJPEG 2.3.1 and earlier allows attackers to crash opj_decompress via a mixed directory of valid and invalid images. In src/bin/jp2/opj_decompress.c, image and stream pointers persist across loop iterations, allowing an error path to destroy an image that a preceding iteration freed. Exploitation requires directory mode to process a mix of valid and invalid images; the supported consequence is abnormal process termination.
The record
- CVE
- CVE-2020-15389
- Published
- Jun 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 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
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