GHSA-X268-QPG6-W9G2
Vulnerability from github – Published: 2024-06-13 19:39 – Updated: 2024-06-13 19:39Summary
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
1. Connect to the TLS server on port 4200 using an openssl client.
2. Initiate a TLS session.
3. Send the renegotiation command ('R') multiple times.
4. 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": [
{
"package": {
"ecosystem": "Maven",
"name": "io.crate:crate"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.7.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-37309"
],
"database_specific": {
"cwe_ids": [
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2024-06-13T19:39:06Z",
"nvd_published_at": "2024-06-13T14:15:13Z",
"severity": "MODERATE"
},
"details": "**Summary** \nClient-Initiated TLS Renegotiation Denial of Service (DoS) Vulnerability at Port 4200\n\n**Details** \nA 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 \u0027R\u0027 initiates renegotiation, followed by the server confirming with \u0027RENEGOTIATING\u0027.\n\n**PoC** \n1. Connect to the TLS server on port 4200 using an openssl client.\n2. Initiate a TLS session.\n3. Send the renegotiation command (\u0027R\u0027) multiple times.\n4. Observe the server response to confirm renegotiation.\n\n**Impact** \nThis 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.\n\n\nTLS 1.3 explicitly forbids renegotiation, since it closes a window of opportunity for an attack.\n",
"id": "GHSA-x268-qpg6-w9g2",
"modified": "2024-06-13T19:39:06Z",
"published": "2024-06-13T19:39:06Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/crate/crate/security/advisories/GHSA-x268-qpg6-w9g2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-37309"
},
{
"type": "WEB",
"url": "https://github.com/crate/crate/commit/1dde03bdf031a20886065195527e368e4a3218b3"
},
{
"type": "WEB",
"url": "https://cratedb.com/docs/crate/reference/en/latest/appendices/release-notes/5.7.2.html"
},
{
"type": "PACKAGE",
"url": "https://github.com/crate/crate"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "CrateDB has a Client initialized Session-Renegotiation DoS"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.