High severity · published Apr 4, 2024
CVE-2024-30255
HTTP/2: CPU exhaustion due to CONTINUATION frame flood
7.5
CVSS
87.8%
EPSS
No
On KEV
Description
Envoy is a cloud-native, open source edge and service proxy. The HTTP/2 protocol stack in Envoy versions prior to 1.29.3, 1.28.2, 1.27.4, and 1.26.8 are vulnerable to CPU exhaustion due to flood of CONTINUATION frames. Envoy's HTTP/2 codec allows the client to send an unlimited number of CONTINUATION frames even after exceeding Envoy's header map limits. This allows an attacker to send a sequence of CONTINUATION frames without the END_HEADERS bit set causing CPU utilization, consuming approximately 1 core per 300Mbit/s of traffic and culminating in denial of service through CPU exhaustion. Users should upgrade to version 1.29.3, 1.28.2, 1.27.4, or 1.26.8 to mitigate the effects of the CONTINUATION flood. As a workaround, disable HTTP/2 protocol for downstream connections.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)87.8% · higher than 100% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EN
envoy · envoyproxy
>= 1.29.0, < 1.29.3; >= 1.28.0, < 1.28.2; >= 1.27.0, < 1.27.4; < 1.26.8 · source: vendor, NVD, CISA
Affected product
EN
envoy
envoyproxy
More from envoy
9.8
CVE-2026-111497
Out-of-Bounds Write in Google Brotli Decoder
7.5
CVE-2023-44487
HTTP/2 Rapid Reset Attack Vulnerability
10.0
CVE-2019-9901
Envoy 1.9.0 and before does not normalize HTTP URL paths
9.8
CVE-2023-35941
Envoy vulnerable to OAuth2 credentials exploit with permanent validity
9.8
CVE-2023-27488
Envoy gRPC client produces invalid protobuf when an HTTP header with non-UTF8 value is received.