# CVE-2024-11403: Out of Bounds Memory Read/Write in libjxl

> An out-of-bounds write in libjxl's JPEG decoder allows attackers to execute arbitrary code or disclose memory when processing untrusted JPEG XL files.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-11403, GHSA-5pp5-4vfv-784q, SUSE-SU-2025:01883-1, UBUNTU-CVE-2024-11403, openSUSE-SU-2024:0402-1

## What is CVE-2024-11403?

CVE-2024-11403 is a medium-severity memory corruption vulnerability in libjxl, published on 25 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-11403?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libjxl` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 0.10.3-150700.4.3.1 |
| `qt6-webengine` | SUSE:Package Hub 15 SP5 | All versions | 6.4.2-bp155.2.6.1 |
| `qt6-webengine-docs` | SUSE:Package Hub 15 SP5 | All versions | 6.4.2-bp155.2.6.1 |
| `qt6-webengine` | openSUSE:Leap 15.5 | All versions | 6.4.2-bp155.2.6.1 |
| `qt6-webengine-docs` | openSUSE:Leap 15.5 | All versions | 6.4.2-bp155.2.6.1 |

Products: Libjxl Project Libjxl.

## How do I fix CVE-2024-11403?

Apply the vendor's patch.

## Is CVE-2024-11403 being exploited?

There is no known exploitation of CVE-2024-11403 in the wild and no public exploit code.

## Other vulnerabilities in libjxl

- [CVE-2021-27804](https://insights.sbomify.com/CVE-2021-27804/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-1837](https://insights.sbomify.com/CVE-2026-1837/): libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2 (high 8.7)
- [CVE-2023-35790](https://insights.sbomify.com/CVE-2023-35790/): Integer overflow in n/a (high 7.5)
- [CVE-2021-36691](https://insights.sbomify.com/CVE-2021-36691/): Denial of service in n/a (high 7.5)
- [CVE-2024-11498](https://insights.sbomify.com/CVE-2024-11498/): Resource exhaustion via Stack overflow in libjxl (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11403 and fix it if it is affected.

What it is: CVE-2024-11403 is a medium-severity memory corruption vulnerability in libjxl, published on 25 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-11403 in the wild and no public exploit code.

Affected product: libjxl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11403/ (Markdown: https://insights.sbomify.com/CVE-2024-11403/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11403
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11403
- OSV: https://osv.dev/vulnerability/CVE-2024-11403

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11403/
Summaries are generated and may contain mistakes; the official description above is the record.