# CVE-2024-45157: Weak cryptography in n/a

> Mbed TLS fails to use the configured HMAC_DRBG algorithm under specific conditions, potentially weakening cryptographic randomness.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2024
- **Updated:** 14 Mar 2025
- **Also known as:** ALPINE-CVE-2024-45157, DEBIAN-CVE-2024-45157, GHSA-cvp8-hm87-hr8x, JLSEC-2025-226, UBUNTU-CVE-2024-45157, openSUSE-SU-2024:14304-1

## What is CVE-2024-45157?

CVE-2024-45157 is a medium-severity vulnerability in n/a, published on 5 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Mbed TLS before 2.28.9 and 3.x before 3.6.1, in which the user-selected algorithm is not used. Unlike previously documented, enabling MBEDTLS_PSA_HMAC_DRBG_MD_TYPE does not cause the PSA subsystem to use HMAC_DRBG: it uses HMAC_DRBG only when MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG and MBEDTLS_CTR_DRBG_C are disabled.

Weakness: CWE-696 (Incorrect Behavior Order)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mbedtls-2` | openSUSE:Tumbleweed | All versions | 2.28.9-1.1 |

Products: Trustedfirmware Mbed Tls.

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

Upgrade to a fixed version.

## Is CVE-2024-45157 being exploited?

There is no known exploitation of CVE-2024-45157 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-34875](https://insights.sbomify.com/CVE-2026-34875/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-49195](https://insights.sbomify.com/CVE-2024-49195/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-45158](https://insights.sbomify.com/CVE-2024-45158/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-45159](https://insights.sbomify.com/CVE-2024-45159/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-45199](https://insights.sbomify.com/CVE-2023-45199/): Mbed TLS 3.2.x through 3.4.x before 3.5 has a Buffer Overflow that can lead to remote Code execution. (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45157 is a medium-severity vulnerability in n/a, published on 5 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45157 in the wild and no public exploit code.

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-45157/ (Markdown: https://insights.sbomify.com/CVE-2024-45157/index.md)
```

## Sources

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

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