CVE-2024-30255: Envoy is a cloud-native, open source edge and service proxy.
High CVSS 7.5
- CVE id
- CVE-2024-30255
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.26.8 >= 1.27.0, < 1.27.4 >= 1.28.0, < 1.28.2 >= 1.29.0, < 1.29.3 |
1.26.8, 1.27.4, 1.28.2, 1.29.3 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.26.8, 1.27.4, 1.28.2, 1.29.3.
envoy --version
- Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.