Application crash via partial JPEG XL decode
Published Dec 31, 2021 · Updated Aug 4, 2024
Out-of-bounds write in libjxl b02d6b9 and libvips 8.11 through 8.11.2 allows local users to crash image-processing applications. ModularFrameDecoder::DecodeGroup mishandles partial decodes when the full modular image is skipped and writes beyond the initialized image storage. Processing a crafted JPEG XL file is required; the demonstrated consequence is a wild-address write and process crash.
Summary
What happened
Out-of-bounds write in libjxl b02d6b9 and libvips 8.11 through 8.11.2 allows local users to crash image-processing applications. ModularFrameDecoder::DecodeGroup mishandles partial decodes when the full modular image is skipped and writes beyond the initialized image storage. Processing a crafted JPEG XL file is required; the demonstrated consequence is a wild-address write and process crash.
The record
- CVE
- CVE-2021-45928
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 31, 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?
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
- OSS-Fuzz minimized JPEG XL testcaseproof 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