Server crash via unrestored ClientHello deframer cursor
Published Dec 6, 2024 · Updated Nov 20, 2025
Denial of service in Rustls 0.23.13 through 0.23.17 allows remote attackers to crash affected TLS servers via a fragmented ClientHello. Acceptor::accept fails to preserve the deframer buffer's processed cursor while parsing the first handshake message, so fragmented input reaches a panic. Exposure requires rustls Acceptor::accept, tokio-rustls LazyConfigAcceptor, or rustls-ffi rustls_acceptor_accept; tokio-rustls TlsAcceptor is unaffected.
Summary
What happened
Denial of service in Rustls 0.23.13 through 0.23.17 allows remote attackers to crash affected TLS servers via a fragmented ClientHello. Acceptor::accept fails to preserve the deframer buffer's processed cursor while parsing the first handshake message, so fragmented input reaches a panic. Exposure requires rustls Acceptor::accept, tokio-rustls LazyConfigAcceptor, or rustls-ffi rustls_acceptor_accept; tokio-rustls TlsAcceptor is unaffected.
The record
- CVE
- CVE-2024-11738
- Published
- Dec 6, 2024
- Updated
- Nov 20, 2025
- Vendor
- Rustls
- Product
- Rustls
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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.23.13 <0.23.18
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- Acceptor::accept panic reproducerproof of concept · demonstrated
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