CVE-2021-22563: Memory Overread in libjxl

Published Nov 1, 2021
·
Updated

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

Affected Software

1 affected component
Libjxl Project Libjxl<0.6.0

Event History

Nov 1, 2021
CVE Published
via MITRE·01:10 PM
Data Sourced
via MITRE·01:10 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2021-22563?

CVE-2021-22563 is considered a high severity vulnerability due to potential segmentation faults and memory corruption.

2

How do I fix CVE-2021-22563?

To fix CVE-2021-22563, upgrade libjxl to a version past 0.6.0 or apply the appropriate patches.

3

What causes CVE-2021-22563?

CVE-2021-22563 is caused by invalid JPEG XL images leading to out of bounds access in libjxl.

4

Which software is affected by CVE-2021-22563?

CVE-2021-22563 affects libjxl versions up to and including 0.6.0.

5

What are the potential consequences of CVE-2021-22563?

The consequences of CVE-2021-22563 include application crashes and possible exposure of sensitive data from memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203