Envoy forwards early CONNECT data in TCP proxy mode
envoyproxy envoy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
envoyproxy envoy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
Envoy is a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, when Envoy is configured in TCP proxy mode to handle CONNECT requests, it accepts client data before issuing a 2xx response and forwards that data to the upstream TCP connection. If a forwarding proxy upstream from Envoy then responds with a non-2xx status, this can cause a de-synchronized CONNECT tunnel state. By default Envoy continues to allow early CONNECT data to avoid disrupting existing deployments. The envoy.reloadable_features.reject_early_connect_data runtime flag can be set to reject CONNECT requests that send data before a 2xx response when intermediaries upstream from Envoy may reject establishment of a CONNECT tunnel.
From the CVE record · GitHub_M
Envoy in TCP proxy mode can forward client data from a CONNECT request before sending a 2xx response. If an upstream forwarding proxy then returns a non-2xx status, the CONNECT tunnel state can become desynchronized. This requires a client to send early CONNECT data; the input does not specify authentication or other user interaction requirements.
Engineers running github.com/envoyproxy/envoy should check versions before 1.33.13, 1.34.0–1.34.10, 1.35.0–1.35.6, and 1.36.0–1.36.2.