CyberRota Analysis
AI-GeneratedEnvoy versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 are vulnerable to an issue where an unauthenticated HTTP/2 client can exploit the handling of non-WebSocket HTTP upgrades, allowing them to smuggle responses to different downstream clients. This vulnerability can lead to unauthorized data exposure and potential manipulation of responses, posing a significant risk to cloud-native applications utilizing Envoy as a proxy. Organizations using affected versions should prioritize upgrading to the patched releases to mitigate this high-severity threat.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy forwards data for a configured non-WebSocket HTTP upgrade before the upstream accepts the upgrade. An unauthenticated HTTP/2 client can place a complete HTTP/1.1 request in extended CONNECT data; Envoy downgrades the request, writes the data unframed to a keep-alive HTTP/1.1 upstream, and returns the socket to the shared pool while the smuggled response remains queued. A different downstream client can then receive the attacker's response. The relevant scope boundary is that webSocket upgrades, plain CONNECT, disabled backend keep-alive, per-downstream pools, and max_requests_per_connection set to 1 are not affected by the demonstrated path. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Related CVEs
Other vulnerabilities affecting the same vendor(s)