Remote server crash via fragmented TLS handshake
Published Nov 12, 2024 · Updated Sep 15, 2025
Heap buffer overflow in Real Time Logic SharkSSL 09.09.24 and earlier allows remote attackers to crash TLS servers via a malformed handshake. An attacker-controlled 16-bit length minus four advances registeredevent beyond the received buffer before SharkSslCon_decrypt dereferences it. Exposure requires TLS 1.2 server mode and a fragmented Client Key Exchange; the confirmed result is process termination and loss of TLS service.
Summary
What happened
Heap buffer overflow in Real Time Logic SharkSSL 09.09.24 and earlier allows remote attackers to crash TLS servers via a malformed handshake. An attacker-controlled 16-bit length minus four advances registeredevent beyond the received buffer before SharkSslCon_decrypt dereferences it. Exposure requires TLS 1.2 server mode and a fragmented Client Key Exchange; the confirmed result is process termination and loss of TLS service.
The record
- CVE
- CVE-2024-48075
- Published
- Nov 12, 2024
- Updated
- Sep 15, 2025
- Vendor
- Real Time Logic
- Product
- SharkSSL
- Classifications
- CWE-122, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Sep 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=09.09.24
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