CVE-2023-29933

llvm-project commit bd456297 was discovered to contain a segmentation fault via the component mlir::Block::getArgument.

Published: 2023-05-05 Last update: 2025-01-29 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-29933 is rated Low Risk (26.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.22%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-29933

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.22% +0.18%
2 2025-03-17 0.05% 0.05% -0.00%
3 2024-11-25 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-29933

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-29933

OS Trackers for CVE-2023-29933

vendor priority summary link
debian unimportant CVE-2023-29933 unimportant priority: Debian including 3 source packages (llvm-toolchain-13, llvm-toolchain-14, llvm-toolchain-15), 4 status rows across 2 suites (bookworm, bullseye): open 4. https://security-tracker.debian.org/tracker/CVE-2023-29933
redhat medium — https://access.redhat.com/security/cve/CVE-2023-29933
ubuntu medium CVE-2023-29933 medium priority: Ubuntu including 3 source packages (llvm-toolchain-13, llvm-toolchain-14, llvm-toolchain-15), 24 status rows across 8 suites (bionic, focal, jammy, kinetic, lunar, trusty, upstream, xenial): ignored 7, DNE 6, not-affected 6, needs-triage 3, released 2. https://ubuntu.com/security/CVE-2023-29933

Affected software / configurations for CVE-2023-29933

Vendor Product Version Raw CPE
llvm llvm 2022-12-11 cpe:2.3:a:llvm:llvm:2022-12-11:*:*:*:*:*:*:*

References for CVE-2023-29933

cvelogic Threat Intelligence