CVE-2024-11498
Resource exhaustion via Stack overflow in libjxl
No known exploitation. EPSS puts it in the 48th percentile. Fixed in 65fbec56bc578b6b6ee02a527be70787bbd053b0.
What to do
Find your product and version, then upgrade to the build on the right.
- LibjxlAffected: ≥ 0.11.0, < 65fbec56bc578b6b6ee02a527be70787bbd053b0Upgrade to: 65fbec56bc578b6b6ee02a527be70787bbd053b0Affected: ≥ 0.10.0-2, < 65fbec56bc578b6b6ee02a527be70787bbd053b0Upgrade to: 65fbec56bc578b6b6ee02a527be70787bbd053b0Affected: ≥ 0.9.0-3, < 65fbec56bc578b6b6ee02a527be70787bbd053b0Upgrade to: 65fbec56bc578b6b6ee02a527be70787bbd053b0Affected: ≥ 0.8.0-3, < 65fbec56bc578b6b6ee02a527be70787bbd053b0Upgrade to: 65fbec56bc578b6b6ee02a527be70787bbd053b0 + 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 a stack buffer overflow in libjxl. A specifically-crafted file can cause the JPEG XL decoder to use large amounts of stack space (up to 256mb is possible, maybe 512mb), potentially exhausting the stack. An attacker can craft a file that will cause excessive memory usage. We recommend upgrading past commit 65fbec56bc578b6b6ee02a527be70787bbd053b0.
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.
- 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 48th 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.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 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 NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- 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.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI