Application crash via invalid JP2 component reference
Published Mar 25, 2021 · Updated Aug 3, 2024
NULL pointer dereference in JasPer before 2.0.27 allows local users to crash an application by opening a crafted JP2 image. The jp2_decode function passes an invalid channel-to-component lookup entry to jas_image_setcmpttype, which writes through a missing component reference. Processing requires a user or consuming application to open the crafted file; the demonstrated consequence is a process crash without data disclosure or modification.
Summary
What happened
NULL pointer dereference in JasPer before 2.0.27 allows local users to crash an application by opening a crafted JP2 image. The jp2_decode function passes an invalid channel-to-component lookup entry to jas_image_setcmpttype, which writes through a missing component reference. Processing requires a user or consuming application to open the crafted file; the demonstrated consequence is a process crash without data disclosure or modification.
The record
- CVE
- CVE-2021-3443
- Published
- Mar 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- JasPer Software
- Product
- JasPer
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 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.27
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
- jasper_poc_v2.026.zipproof 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