Stack corruption via unchecked curve bit size
Published Sep 5, 2024 · Updated Nov 25, 2024
Stack buffer overflow in Mbed TLS 3.6.0 allows attackers to corrupt stack memory through attacker-controlled ECDSA conversion input. The mbedtls_ecdsa_der_to_raw() and mbedtls_ecdsa_raw_to_der() functions size stack buffers without correctly validating bits against the largest supported curve. Exploitation requires an application to call either function directly with attacker-controlled input and declared curve size; internal library calls are safe.
Summary
What happened
Stack buffer overflow in Mbed TLS 3.6.0 allows attackers to corrupt stack memory through attacker-controlled ECDSA conversion input. The mbedtls_ecdsa_der_to_raw() and mbedtls_ecdsa_raw_to_der() functions size stack buffers without correctly validating bits against the largest supported curve. Exploitation requires an application to call either function directly with attacker-controlled input and declared curve size; internal library calls are safe.
The record
- CVE
- CVE-2024-45158
- Published
- Sep 5, 2024
- Updated
- Nov 25, 2024
- Vendor
- TrustedFirmware.org
- Product
- Mbed TLS
- Classifications
- CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6 <3.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo