CVE-2024-45157: 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.
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: CBL Mariner 2.0 ARM 1.0.1-6; CBL Mariner 2.0 x64 1.0.1-6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to CBL Mariner 2.0 ARM 1.0.1-6; CBL Mariner 2.0 x64 1.0.1-6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 5, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-696
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| trustedfirmware | mbed tls | cpe:2.3:a:trustedfirmware:mbed_tls |
Check your server's TLS configuration
The Mbed TLS version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- trustedfirmware mbed tls2.26.0 and later · before 2.28.9
- trustedfirmware mbed tls3.2.0 and later · before 3.6.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.17 | mbedtls | before 2.28.9-r0 | 2.28.9-r0 |
| Alpine:v3.20 | mbedtls | before 3.6.1-r0 | 3.6.1-r0 |
| Alpine:v3.21 | mbedtls2 | before 2.28.10-r0 | 2.28.10-r0 |
| Alpine:v3.24 | mbedtls3 | before 3.6.1-r0 | 3.6.1-r0 |
| Debian:12 | mbedtls | from 0 | — |
| Debian:13 | mbedtls | before 3.6.2-1 | 3.6.2-1 |
| openSUSE:Leap 16.0 | mbedtls-2 | before 2.28.10-bp160.1.1 | 2.28.10-bp160.1.1 |
| openSUSE:Tumbleweed | mbedtls-2 | before 2.28.9-1.1 | 2.28.9-1.1 |
Same product
trustedfirmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-34875An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0.39Monitor
- CVE-2024-49195Mbed TLS 3.5.x through 3.6.x before 3.6.2 has a buffer underrun in pkwrite when writing an opaque key pair39Monitor
- CVE-2024-45159An issue was discovered in Mbed TLS 3.x before 3.6.1.39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-28836Apr 2, 2024 · An issue was discovered in Mbed TLS 3.5.x before 3.6.0.21Monitor
- ← EarlierCVE-2024-30166Apr 2, 2024 · In Mbed TLS 3.3.0 through 3.5.2 before 3.6.0, a malicious client can cause information disclosure or a denial of service because of a stack 36Monitor
- Later →CVE-2024-45158Sep 5, 2024 · An issue was discovered in Mbed TLS 3.6 before 3.6.1.39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| CBL Mariner 2.0 ARM | 1.0.1-6 · hvloader | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 1.0.1-6 · hvloader | Microsoft (MSRC) |
| alpine:mbedtls | 2.28.9-r0 · Alpine:v3.17 | Package registry (OSV) |
| alpine:mbedtls2 | 2.28.10-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:mbedtls3 | 3.6.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:mbedtls | 3.6.2-1 · Debian:13 | Package registry (OSV) |
| opensuse:mbedtls-2 | 2.28.9-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1404 · Sep 6, 2024(Mbed TLS Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-696 · Incorrect Behavior OrderCVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.