Unauthenticated TLS server crash via length underflow
Published Jan 23, 2025 · Updated Feb 27, 2025
Heap buffer overflow in SharkSSL commit 64808a5 allows remote attackers to crash TLS 1.2 servers with a malformed ClientHello. In handleptrauth, repeated subtraction from the attacker-controlled unsigned Extension Length wraps len to a large value while registeredevent advances and is dereferenced beyond the ClientHello buffer. No authentication or user interaction is required; the demonstrated outcome is an out-of-bounds read that terminates the TLS server, not confirmed code execution.
Summary
What happened
Heap buffer overflow in SharkSSL commit 64808a5 allows remote attackers to crash TLS 1.2 servers with a malformed ClientHello. In handleptrauth, repeated subtraction from the attacker-controlled unsigned Extension Length wraps len to a large value while registeredevent advances and is dereferenced beyond the ClientHello buffer. No authentication or user interaction is required; the demonstrated outcome is an out-of-bounds read that terminates the TLS server, not confirmed code execution.
The record
- CVE
- CVE-2024-53379
- Published
- Jan 23, 2025
- Updated
- Feb 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 27, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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