# CVE-2024-50382: Information disclosure in n/a

> Compiler-induced secret-dependent control flow in Botan's GHASH implementation may leak cryptographic secrets via timing side-channels on specific LLVM versions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Oct 2024
- **Updated:** 24 Oct 2024
- **Also known as:** AZL-51678, AZL-51707, DEBIAN-CVE-2024-50382, GHSA-p27h-83pf-6hh9, OESA-2024-2328, OESA-2024-2329, OESA-2024-2330, ROOT-OS-ALPINE-319-CVE-2024-50382, ROOT-OS-ALPINE-320-CVE-2024-50382, UBUNTU-CVE-2024-50382, openSUSE-SU-2024:14429-1

## What is CVE-2024-50382?

CVE-2024-50382 is a medium-severity vulnerability in n/a, published on 23 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2024-50382?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Botan` | openSUSE:Tumbleweed | All versions | 3.6.0-1.1 |

Products: Botan Project Botan.

## How do I fix CVE-2024-50382?

Upgrade to a fixed version.

## Is CVE-2024-50382 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50382 exists.

## Other vulnerabilities in n/a

- [CVE-2021-24115](https://insights.sbomify.com/CVE-2021-24115/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-9127](https://insights.sbomify.com/CVE-2018-9127/): Security feature bypass in n/a (critical 9.8)
- [CVE-2015-7826](https://insights.sbomify.com/CVE-2015-7826/): Security feature bypass in n/a (critical 9.8)
- [CVE-2016-6878](https://insights.sbomify.com/CVE-2016-6878/): Other in n/a (critical 9.8)
- [CVE-2016-9132](https://insights.sbomify.com/CVE-2016-9132/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50382 and fix it if it is affected.

What it is: CVE-2024-50382 is a medium-severity vulnerability in n/a, published on 23 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50382 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50382/ (Markdown: https://insights.sbomify.com/CVE-2024-50382/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50382
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50382
- OSV: https://osv.dev/vulnerability/CVE-2024-50382

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50382/
Summaries are generated and may contain mistakes; the official description above is the record.