First published: Thu Apr 04 2024(Updated: )
Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceeded. This allows an attacker to send an sequence of CONTINUATION frames without the END_HEADERS bit set causing unlimited memory consumption. This can lead to denial of service through memory exhaustion. Users should upgrade to versions 1.29.2 to mitigate the effects of the CONTINUATION flood. Note that this vulnerability is a regression in Envoy version 1.29.0 and 1.29.1 only. As a workaround, downgrade to version 1.28.1 or earlier or disable HTTP/2 protocol for downstream connections.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Envoy Envoy | >=1.29.0<=1.29.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-27919 is considered a high severity vulnerability due to its potential for denial-of-service attacks.
To fix CVE-2024-27919, upgrade Envoy to version 1.29.2 or later.
CVE-2024-27919 affects Envoy versions 1.29.0 and 1.29.1.
CVE-2024-27919 can be exploited through a flood of CONTINUATION frames, potentially leading to a denial of service.
Detailed information about CVE-2024-27919 is available in the release notes and security advisories from the Envoy project.