HTTP/2: CPU exhaustion due to CONTINUATION frame flood
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 85%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| envoyproxy | <1.26.8, >=1.27.0 <1.27.4, >=1.28.0 <1.28.2, >=1.29.0 <1.29.3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket