CVE-2024-37309 is a medium-severity (CVSS 5.3) CWE-770 vulnerability in io.crate:crate. A fix is available for io.crate:crate — see the affected versions and patch details below.
Client initialized Session-Renegotiation DoS
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-37309.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.crate:crateReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Client-Initiated TLS Renegotiation Denial of Service (DoS) Vulnerability at Port 4200
Details
A high-risk vulnerability has been identified where the TLS endpoint (port 4200) permits client-initiated renegotiation. In this scenario, an attacker can exploit this feature to repeatedly request renegotiation of security parameters during an ongoing TLS session. This flaw could lead to excessive consumption of CPU resources, resulting in potential server overload and service disruption. The vulnerability was confirmed using an openssl client where the command 'R' initiates renegotiation, followed by the server confirming with 'RENEGOTIATING'.
PoC
- Connect to the TLS server on port 4200 using an openssl client.
- Initiate a TLS session.
- Send the renegotiation command ('R') multiple times.
- Observe the server response to confirm renegotiation.
Impact
This vulnerability allows an attacker to perform a denial of service attack by exhausting server CPU resources through repeated TLS renegotiations. This impacts the availability of services running on the affected server, posing a significant risk to operational stability and security.
TLS 1.3 explicitly forbids renegotiation, since it closes a window of opportunity for an attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.crate:crate | all versions | 5.7.2io.crate:crate:5.7.2 |
Affected Products
cratedbcratedbDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.crate:crate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.crate:crate to 5.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-37309 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2024-37309 in your dependencies?
Find it across Maven, including transitive dependencies.