Application crash via unchecked JP2 component mismatches
Published Feb 23, 2021 · Updated Aug 3, 2024
Null pointer dereference in JasPer before 2.0.25 allows context-dependent attackers to crash an image-processing application via a crafted JP2 file. The jp2_decode function merely warns when JP2 header or BPCC component counts and types conflict with the decoded codestream, then continues into an invalid state that dereferences a null image pointer. A target application must process the crafted file, and the demonstrated consequence is interruption of that process rather than data disclosure or modification.
Summary
What happened
Null pointer dereference in JasPer before 2.0.25 allows context-dependent attackers to crash an image-processing application via a crafted JP2 file. The jp2_decode function merely warns when JP2 header or BPCC component counts and types conflict with the decoded codestream, then continues into an invalid state that dereferences a null image pointer. A target application must process the crafted file, and the demonstrated consequence is interruption of that process rather than data disclosure or modification.
The record
- CVE
- CVE-2021-26927
- Published
- Feb 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- JasPer Project
- Product
- JasPer Image Coding Toolkit
- Classifications
- CWE-476
- 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=before 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.
Weakness, pattern, technique
Public exploit references
- jp2_decode null-pointer access reproducerproof 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