Security Resilience

CVE-2023-35790

Memory Safety in Libjxl Project Libjxl ≤ 0.8.2

Published
16 June 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0077 56th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-35790 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Libjxl Project Libjxl. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An issue was discovered in dec_patch_dictionary.cc in libjxl before 0.8.2. An integer underflow in patch decoding can lead to a denial of service, such as an infinite loop.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-12474Same product: Libjxl Project Libjxl
CVE-2023-0645Same product: Libjxl Project Libjxl
CVE-2024-11403Same product: Libjxl Project Libjxl
CVE-2026-1837Same product: Libjxl Project Libjxl
CVE-2024-11498Same product: Libjxl Project Libjxl
CVE-2026-33999Shared CWE-191
CVE-2026-3084Shared CWE-191
CVE-2024-21466Shared CWE-191
CVE-2026-9624Shared CWE-191
CVE-2023-36794Shared CWE-191

Affected Assets

libjxl project
libjxl
≤ 0.8.2

Mitigating Controls

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 full match
blocks

Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.

ID.RA-01 partial match
blocks

Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.

PR.PS-02 partial match
blocks

Routine patching can remediate known underflow bugs once they are discovered in deployed software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development catches integer underflow defects before release.

prevents

Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.

prevents

A.8.30’s contractual secure-design, coding, and testing requirements reduce the introduction of integer-underflow defects in outsourced software, but fallible implementation practice leaves a substantial remainder.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. Integer underflow is primarily a first-party code defect discoverable by static analysis or code review, which A.8.8 does not reach. A.8.8 finds this weakness only where it has been published as a CVE in a third-party component, which is a minority of latent instances.

References