GHSA-RJ35-4M94-77JH
Envoy forwards early CONNECT data in TCP proxy mode
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v1.33.13 | github.com/envoyproxy/envoy · -2 d desde divulgación | |
| Remediación | Parche v1.34.11 | github.com/envoyproxy/envoy · -2 d desde divulgación | |
| Remediación | Parche v1.35.7 | github.com/envoyproxy/envoy · -1 d desde divulgación | |
| Remediación | Parche v1.36.3 | github.com/envoyproxy/envoy · -1 d desde divulgación | |
| Divulgación | Publicada | GHSA-RJ35-4M94-77JH divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Summary
Forwarding of early CONNECT data in TCP proxy mode.
Details
Per RFC 7231-4.3.6 https://www.rfc-editor.org/rfc/rfc7231#section-4.3.6 the sender of CONNECT (and all inbound proxies) switch to tunnel mode only after receiving 2xx response. However in TCP proxy mode, Envoy accepts client data before it has issued a 2xx response and eagerly proxies it to an established TCP connection. This creates possibility of a de-synchronized tunnel state if a proxy upstream from Envoy responds with a status other an 2xx.
The RFC does not specify the behavior in case an early CONNECT data is received and early CONNECT data is common as a latency reduction mechanism. To prevent disruption to existing deployments Envoy will by default allow early CONNECT data. Setting the `envoy.reloadable_features.reject_early_connect_data` runtime flag to `true` will cause CONNECT requests that send data before 2xx response to be rejected. This options should be enabled if there are intermediaries upstream from Envoy that may reject establishment of a CONNECT tunnel.
Impact
De-synchronization of CONNECT tunnel state if a forwarding proxy upstream from Envoy responds with a non 2xx status.
## Attack vector(s)
Sending data for a CONNECT request before receiving 2xx response.
## Patches
Users should upgrade to v1.36.3, v1.35.7, v1.34.11 or v1.33.13
Credits
chasingimpact https://github.com/chasingimpact (Patrick)
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/envoyproxy/envoy |
Corregida | v1.33.13, v1.34.11, v1.35.7, v1.36.3 | -2 d · -2 d · -1 d · -1 d | v1.40.2 no afectada |
1.33.13v1.33.131.34.11v1.34.111.35.7v1.35.71.36.3v1.36.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2025-64763https://github.com/envoyproxy/envoy/security/advisories/GHSA-rj35-4m94-77jhhttps://github.com/envoyproxy/envoyLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
