Envoy
Envoy: Cross-user response poisoning via a generic (non-WebSocket) HTTP upgrade on Envoy's shared backend pool
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.36.10
- >= 1.37.0, < 1.37.6
- >= 1.38.0, < 1.38.4
- >= 1.39.0, < 1.39.1
Fixed in 1.36.10, 1.37.6, 1.38.4, 1.39.1
Mitigation
Upgrade envoy to 1.36.10 or 1.37.6 or 1.38.4 or 1.39.1 or later.
References
- Vendor advisory github.com/envoyproxy/envoy/security/advisorie…
- Patch github.com/envoyproxy/envoy/commit/30985562696…
- Patch github.com/envoyproxy/envoy/commit/3c7998545a9…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.