CVE-2024-23326: Envoy incorrectly accepts HTTP 200 response for entering upgrade mode
envoyproxy · envoy
Affected: envoyproxy · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 30% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- envoyproxy · envoy>= 1.13.0, <= 1.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- envoyproxy
- Published
- June 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2024-23326 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.