Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2023-39787
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
CVEs Like This One
Affected Assets
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.
Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
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.
Security testing in development catches integer underflow defects before release.
Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.
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.
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.