Cyber Resilience

CVE-2023-29935

Llvm 2022-11-23

Published
05 May 2023
Modified
29 January 2025
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0022 13th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2023-29935 is a medium-severity Reachable Assertion (CWE-617) vulnerability in Llvm Llvm. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

llvm-project commit a0138390 was discovered to contain an assertion failure at !replacements.count(op) && "operation was already replaced.

CWE(s)
CWE-617

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-29942Same product: Llvm Llvm
CVE-2023-29932Same product: Llvm Llvm
CVE-2023-29934Same product: Llvm Llvm
CVE-2023-29939Same product: Llvm Llvm
CVE-2023-29941Same product: Llvm Llvm
CVE-2023-26924Same product: Llvm Llvm
CVE-2023-29933Same product: Llvm Llvm
CVE-2024-56783Shared CWE-617
CVE-2025-8804Shared CWE-617
CVE-2024-39509Shared CWE-617

Affected Assets

llvm
llvm
2022-11-23

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
prevents

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect reachable assertions before release, reducing the likelihood of exploitation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates defensive coding and input validation that prevent reachable assertions from being triggered by untrusted data.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify that assertions must not be reachable from attacker-controlled inputs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage the use of assertions for runtime error handling that an attacker could exploit.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

References