Memory corruption via unchecked opaque-key output copy
Published Oct 15, 2024 · Updated Nov 25, 2024
Buffer underrun in Mbed TLS 3.5.0 through 3.6.1 allows attackers to corrupt stack or heap memory during opaque-key export. The key-writing functions copy data from an intermediate buffer into an undersized caller buffer without checking the destination capacity. Reachability requires MBEDTLS_USE_PSA_CRYPTO, an opaque key context, and one of the documented undersized DER or PEM output cases.
Summary
What happened
Buffer underrun in Mbed TLS 3.5.0 through 3.6.1 allows attackers to corrupt stack or heap memory during opaque-key export. The key-writing functions copy data from an intermediate buffer into an undersized caller buffer without checking the destination capacity. Reachability requires MBEDTLS_USE_PSA_CRYPTO, an opaque key context, and one of the documented undersized DER or PEM output cases.
The record
- CVE
- CVE-2024-49195
- Published
- Oct 15, 2024
- Updated
- Nov 25, 2024
- Vendor
- TrustedFirmware.org
- Product
- Mbed TLS
- Classifications
- CWE-787
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 15, 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.5.0 <3.6.2
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