CVE-2024-45158 json
An issue was discovered in Mbed TLS 3.6 before 3.6.1.
published 2y ago modified 4mo ago also EUVD-2024-41674
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
An issue was discovered in Mbed TLS 3.6 before 3.6.1. A stack buffer overflow in mbedtls_ecdsa_der_to_raw() and mbedtls_ecdsa_raw_to_der() can occur when the bits parameter is larger than the largest supported curve. In some configurations with PSA disabled, all values of bits are affected. (This never happens in internal library calls, but can affect applications that call these functions directly.)
Patch / fix
- mbed mbedtls 3.6.1
- mbedtls Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 3.6.1-r0
- mbedtls3 Alpine 3.24 3.6.1-r0
alpine advisories ALPINE-CVE-2024-45158
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2024-45158 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- mbed mbedtls
Classification
- Weakness
-
- CWE-121 Stack-based Buffer Overflow
References
-
mbed-tls.readthedocs.io
/en/latest/security-advisories/
vendor-advisory
-
mbed-tls.readthedocs.io
/en/latest/security-advisories/mbedtls-security-advisory-2024-08-2/
vendor-advisory
-
github.com
/Mbed-TLS/mbedtls/releases/
release-notes
Sources
- CVE List CVE-2024-45158
- NVD CVE-2024-45158
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.