Information disclosure or service interruption via ClientHello over-read
Published Apr 3, 2024 · Updated Aug 2, 2024
Stack buffer over-read in Arm Mbed TLS 3.3.0 through 3.5.2 allows remote attackers to disclose memory or interrupt TLS servers. The TLS 1.3 ClientHello parser reads fewer than 256 bytes beyond a stack buffer while processing a crafted hello on servers supporting a PSK key exchange mode. The server must enable TLS 1.3 and an affected PSK mode; no authentication is required, and exploitation can disclose memory or stop the TLS service.
Summary
What happened
Stack buffer over-read in Arm Mbed TLS 3.3.0 through 3.5.2 allows remote attackers to disclose memory or interrupt TLS servers. The TLS 1.3 ClientHello parser reads fewer than 256 bytes beyond a stack buffer while processing a crafted hello on servers supporting a PSK key exchange mode. The server must enable TLS 1.3 and an affected PSK mode; no authentication is required, and exploitation can disclose memory or stop the TLS service.
The record
- CVE
- CVE-2024-30166
- Published
- Apr 3, 2024
- Updated
- Aug 2, 2024
- Vendor
- Arm
- Product
- Mbed TLS
- Classifications
- CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.3.0 <3.6.0
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