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.
Metrics
Affected Vendors & Products
References
History
Tue, 26 Nov 2024 03:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Mon, 25 Nov 2024 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Mon, 25 Nov 2024 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | Out of Bounds Memory Read/Write in libjxl | |
Weaknesses | CWE-125 CWE-787 |
|
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: Google
Published: 2024-11-25T13:08:38.280Z
Updated: 2024-11-25T13:54:29.806Z
Reserved: 2024-11-19T11:20:39.008Z
Link: CVE-2024-11403

Updated: 2024-11-25T13:54:25.883Z

Status : Received
Published: 2024-11-25T14:15:06.310
Modified: 2024-11-25T14:15:06.310
Link: CVE-2024-11403
