CVE Tools

CVE-2024-11403

Out of Bounds Memory Read/Write in libjxl

No known exploitation. EPSS puts it in the 50th percentile. Fixed in 9cc451b91b74ba470fd72bd48c121e9f33d24c99.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • LibjxlAffected: ≥ 0.11.0, < 9cc451b91b74ba470fd72bd48c121e9f33d24c99Upgrade to: 9cc451b91b74ba470fd72bd48c121e9f33d24c99Affected: ≥ 0.10.0-2, < 9cc451b91b74ba470fd72bd48c121e9f33d24c99Upgrade to: 9cc451b91b74ba470fd72bd48c121e9f33d24c99Affected: ≥ 0.9.0-3, < 9cc451b91b74ba470fd72bd48c121e9f33d24c99Upgrade to: 9cc451b91b74ba470fd72bd48c121e9f33d24c99Affected: ≥ 0.8.0-3, < 9cc451b91b74ba470fd72bd48c121e9f33d24c99Upgrade to: 9cc451b91b74ba470fd72bd48c121e9f33d24c99 + 1 more branchStated by: CVE record
  • ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
  • ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.8Upgrade to: not statedStated by: BDU
  • Сообщество свободного программного обеспечения LibjxlAffected: от 0.7.0 до 0.7.2Upgrade to: not statedStated by: BDU
  • АО «НППКТ» ОСОН ОСнова ОnyxAffected: до 3.1Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS50th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 577 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Libjxl, not every advisory.