Service interruption via client-initiated TLS renegotiation
Published Jun 13, 2024 · Updated Aug 2, 2024
TLS renegotiation in CrateDB before 5.7.2 allows remote attackers to interrupt service through repeated requests on port 4200. The TLS 1.2 endpoint accepts client-initiated renegotiation during an established session, repeatedly performing CPU-intensive security handshakes. Network access to a TLS-enabled cluster is sufficient; sustained renegotiation requests exhaust server CPU and overload the database service.
Summary
What happened
TLS renegotiation in CrateDB before 5.7.2 allows remote attackers to interrupt service through repeated requests on port 4200. The TLS 1.2 endpoint accepts client-initiated renegotiation during an established session, repeatedly performing CPU-intensive security handshakes. Network access to a TLS-enabled cluster is sufficient; sustained renegotiation requests exhaust server CPU and overload the database service.
The record
- CVE
- CVE-2024-37309
- Published
- Jun 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Crate.io
- Product
- CrateDB
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 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=0 <5.7.2
- Affected versionversion=< 5.7.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
- Client-initiated TLS renegotiation PoCproof 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