Crash or memory disclosure via undersized spline cache
Published Nov 1, 2021 · Updated Sep 17, 2024
Out-of-bounds read in Google libjxl 0.6.0 and earlier allows local users to crash decoders or disclose memory via a crafted image. ProcessDCGlobal initializes the spline draw cache with unpadded frame dimensions, so DrawSegments can index segment_y_start beyond its allocated rows when larger upsampled coordinates are used. Triggering the flaw requires decoding an invalid JPEG XL image containing splines; consequences are a crash or unintended pixels derived from process memory.
Summary
What happened
Out-of-bounds read in Google libjxl 0.6.0 and earlier allows local users to crash decoders or disclose memory via a crafted image. ProcessDCGlobal initializes the spline draw cache with unpadded frame dimensions, so DrawSegments can index segment_y_start beyond its allocated rows when larger upsampled coordinates are used. Triggering the flaw requires decoding an invalid JPEG XL image containing splines; consequences are a crash or unintended pixels derived from process memory.
The record
- CVE
- CVE-2021-22563
- Published
- Nov 1, 2021
- Updated
- Sep 17, 2024
- Vendor
- Go standard library
- Product
- libjxl
- Classifications
- CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 1, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=unspecified <=0.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- 161-byte spline decoding crash sampleproof 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