Code execution via malformed permutation decoding
Published Mar 5, 2021 · Updated Aug 3, 2024
Heap buffer overflow in jpeg-xl 0.3.2 allows context-dependent attackers to execute code by supplying a malicious JXL file. ReadPermutation in lib/jxl/coeff_order.cc performs an out-of-bounds heap write during djxl decoding, but the public issue does not identify the unchecked value. Execution requires a user to decode the crafted file; successful corruption can crash djxl or execute code in its process.
Summary
What happened
Heap buffer overflow in jpeg-xl 0.3.2 allows context-dependent attackers to execute code by supplying a malicious JXL file. ReadPermutation in lib/jxl/coeff_order.cc performs an out-of-bounds heap write during djxl decoding, but the public issue does not identify the unchecked value. Execution requires a user to decode the crafted file; successful corruption can crash djxl or execute code in its process.
The record
- CVE
- CVE-2021-28026
- Published
- Mar 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 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?
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
- GitLab issue 163 proof-of-concept JXL fileproof 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