CVE-2024-11403: Out of Bounds Memory Read/Write in libjxl
There exists an out of bounds read/write in LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99. The JPEG decoder used by the JPEG XL encoder when doing JPEG recompression (i.e. if using JxlEncoderAddJPEGFrame on untrusted input) does not properly check bounds in the presence of incomplete codes. This could lead to an out-of-bounds write. In jpegli which is released as part of the same project, the same vulnerability is present. However, the relevant buffer is part of a bigger structure, and the code makes no assumptions on the values that could be overwritten. The issue could however cause jpegli to read uninitialised memory, or addresses of functions.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-11403?
CVE-2024-11403 is considered a high-severity vulnerability due to the potential for out of bounds read/write exploits in affected software.
How do I fix CVE-2024-11403?
To fix CVE-2024-11403, upgrade to LibJXL versions post commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99.
Which versions are affected by CVE-2024-11403?
CVE-2024-11403 affects LibJXL versions prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99.
What type of vulnerability is CVE-2024-11403?
CVE-2024-11403 is an out of bounds read/write vulnerability related to the JPEG decoder in LibJXL.
What software products are impacted by CVE-2024-11403?
CVE-2024-11403 impacts Google libjxl and jpegli products prior to commit 9cc451b91b74ba470fd72bd48c121e9f33d24c99.