Decoder crash via out-of-bounds border copy
Published Nov 1, 2021 · Updated Sep 17, 2024
Heap buffer overflow in libjxl 0.6.0 and earlier allows local users to crash decoding processes via crafted JPEG XL images. LoadBorders() copies the right or bottom border from a nonexistent next group when an undersized edge group is decoded out of order. Triggering requires a slightly oversized image and out-of-order group processing caused by file ordering or heavily loaded multithreaded decoding, producing an out-of-bounds heap read and write.
Summary
What happened
Heap buffer overflow in libjxl 0.6.0 and earlier allows local users to crash decoding processes via crafted JPEG XL images. LoadBorders() copies the right or bottom border from a nonexistent next group when an undersized edge group is decoded out of order. Triggering requires a slightly oversized image and out-of-order group processing caused by file ordering or heavily loaded multithreaded decoding, producing an out-of-bounds heap read and write.
The record
- CVE
- CVE-2021-22564
- Published
- Nov 1, 2021
- Updated
- Sep 17, 2024
- Vendor
- Go standard library
- Product
- libjxl
- Classifications
- CWE-122, CWE-787, T1204.002
- 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
- Concurrent decoding crash reproducerfunctional · 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