CVE-2024-23326 Envoy incorrectly accepts HTTP 200 response for entering upgrade mode
Attackers can potentially smuggle requests through Envoy if a backend server incorrectly sends a 200 status with an upgrade header, bypassing protocol expectations.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-23326?
CVE-2024-23326 is a medium-severity vulnerability in Envoyproxy Envoy, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Envoy is a cloud-native, open source edge and service proxy. A theoretical request smuggling vulnerability exists through Envoy if a server can be tricked into adding an upgrade header into a response. Per RFC https://www.rfc-editor.org/rfc/rfc7230#section-6.7 a server sends 101 when switching protocols. Envoy incorrectly accepts a 200 response from a server when requesting a protocol upgrade, but 200 does not indicate protocol switch. This opens up the possibility of request smuggling through Envoy if the server can be tricked into adding the upgrade header to the response.
Which versions are affected by CVE-2024-23326?
1 open source package ship an affected version, including envoy. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
envoy Bitnami | All versions | 1.27.6, 1.28.4, 1.29.5, 1.30.2 |
Products include Envoyproxy Envoy.
How do I fix CVE-2024-23326?
Upgrade envoy to a fixed version for your release line: 1.27.6, 1.28.4, 1.29.5 or 1.30.2.
Is CVE-2024-23326 being exploited?
There is no known exploitation of CVE-2024-23326 in the wild and no public exploit code.
Other vulnerabilities in Envoyproxy Envoy
Sources
Also known as BIT-envoy-2024-23326, GHSA-vcf8-7238-v74c.