CVE-2024-50382

Exp

Botan before 3.6.0, when certain LLVM versions are used, has compiler-induced secret-dependent control flow in lib/utils/ghash/ghash.cpp in GHASH in AES-GCM. There is a branch instead of an XOR with carry. This was observed for Clang in LLVM 15 on RISC-V.

Published: 2024-10-23 Last update: 2025-07-10 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-50382 is rated Exploit Available (51.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.16%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2024-50382

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-50382

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-05-22 0.11% 0.16% +0.05%
2 2025-12-01 0.16% 0.11% -0.05%
3 2025-08-19 — 0.16% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-50382

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-50382

OS Trackers for CVE-2024-50382

vendor priority summary link
alpine — CVE-2024-50382: 1 source package rows (botan); 34 state rows across 6 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, edge-main); fixed 0, open 34. https://security.alpinelinux.org/vuln/CVE-2024-50382
debian unimportant CVE-2024-50382 unimportant priority: Debian including 1 source packages (botan), 3 status rows across 3 suites (bookworm, bullseye, trixie): resolved 2, open 1. https://security-tracker.debian.org/tracker/CVE-2024-50382
suse medium CVE-2024-50382 severity moderate: SUSE including 29 source package names (Botan, Botan-2.19.5-bp155.2.6.1, …), 68 product×package rows across 13 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP5, SUSE Linux Enterprise Module for Package Hub 15 SP6, … (13 product lines)): Fixed 41, Known Not Affected 27. https://www.suse.com/security/cve/CVE-2024-50382/
ubuntu medium CVE-2024-50382 medium priority: Ubuntu including 3 source packages (botan, oscar, thunderbird), 22 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): not-affected 7, needs-triage 6, released 4, ignored 3, DNE 1, needed 1. https://ubuntu.com/security/CVE-2024-50382

Affected software / configurations for CVE-2024-50382

Vendor Product Version Raw CPE
botan_project botan < 3.6.0 cpe:2.3:a:botan_project:botan:*:*:*:*:*:*:*:*

References for CVE-2024-50382

cvelogic Threat Intelligence