libjxl: Out-of-bounds Read
CVE-2024-11403 is a critical-severity out-of-bounds read vulnerability in libjxl, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 9cc451b91b74ba470fd72bd48c121e9f33d24c99 as the first without the flaw, so updating libjxl to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.63% chance of exploitation within 30 days, higher than 51% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update libjxl to 9cc451b91b74ba470fd72bd48c121e9f33d24c99 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Libjxl | libjxl | 0.11.0 up to, but not including, 9cc451b91b74ba470fd72bd48c121e9f33d24c99; 0.10.0-2 up to, but not including, 9cc451b91b74ba470fd72bd48c121e9f33d24c99; 0.9.0-3 up to, but not including, 9cc451b91b74ba470fd72bd48c121e9f33d24c99; 0.8.0-3 up to, but not including, 9cc451b91b74ba470fd72bd48c121e9f33d24c99; 0.7.0-1 up to, but not including, 9cc451b91b74ba470fd72bd48c121e9f33d24c99 | 9cc451b91b74ba470fd72bd48c121e9f33d24c99 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.9 | Medium | CNA (google.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other vulnerabilities in libjxl
- 7.5 High severity
- 9.1 Critical severity
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.8 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.