CVE-2021-22563 Memory Overread in libjxl
An out-of-bounds read in libjxl when rendering splines can cause crashes or leak memory, requiring an upgrade to fix.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2021-22563?
CVE-2021-22563 is a medium-severity memory corruption vulnerability in Google LLC libjxl, published on 1 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Invalid JPEG XL images using libjxl can cause an out of bounds access on a std::vector<std::vector<T>> when rendering splines. The OOB read access can either lead to a segfault, or rendering splines based on other process memory. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/757
Which versions are affected by CVE-2021-22563?
It affects 1 product.
Products include Libjxl Project Libjxl.
How do I fix CVE-2021-22563?
No fix has been published for CVE-2021-22563 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2021-22563 being exploited?
There is no known exploitation of CVE-2021-22563 in the wild and no public exploit code.
Other vulnerabilities in Google LLC libjxl
Sources
Also known as GHSA-q2wp-4p9r-fg6g.