Information disclosure or crash via JP2 component mismatch
Published Feb 23, 2021 · Updated Aug 3, 2024
Out-of-bounds read in JasPer before 2.0.25 allows attackers to disclose memory or crash applications via crafted JP2 images. The jp2_decode routine continued decoding when JP2 headers reported inconsistent component counts or data types, issuing warnings instead of stopping and enabling reads beyond valid buffers. Processing a malicious image is required, so impact depends on an application or user opening attacker-supplied JP2 content; consequences are limited to memory disclosure or process crash.
Summary
What happened
Out-of-bounds read in JasPer before 2.0.25 allows attackers to disclose memory or crash applications via crafted JP2 images. The jp2_decode routine continued decoding when JP2 headers reported inconsistent component counts or data types, issuing warnings instead of stopping and enabling reads beyond valid buffers. Processing a malicious image is required, so impact depends on an application or user opening attacker-supplied JP2 content; consequences are limited to memory disclosure or process crash.
The record
- CVE
- CVE-2021-26926
- Published
- Feb 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- JasPer Software
- Product
- JasPer
- Classifications
- CWE-125, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 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=jasper 2.0.25
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.
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