Memory corruption via incorrect encoder offsets
Published May 13, 2021 · Updated Aug 4, 2024
Out-of-bounds write in OpenJPEG before 2.4.0 allows local users to corrupt memory via crafted x,y offsets during encoding. The pngtoimage function computes image x1 and y1 by adding image offsets twice, producing incorrect bounds and a heap buffer overflow. Exploitation requires a user or process to run the encoder on attacker-controlled input; impact can include memory disclosure, data corruption, or service interruption.
Summary
What happened
Out-of-bounds write in OpenJPEG before 2.4.0 allows local users to corrupt memory via crafted x,y offsets during encoding. The pngtoimage function computes image x1 and y1 by adding image offsets twice, producing incorrect bounds and a heap buffer overflow. Exploitation requires a user or process to run the encoder on attacker-controlled input; impact can include memory disclosure, data corruption, or service interruption.
The record
- CVE
- CVE-2020-27823
- Published
- May 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Université catholique de Louvain
- Product
- OpenJPEG
- Classifications
- CWE-120, CWE-787, CWE-20, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=openjpeg 2.4.0
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