← voltar
CVE-2026-55568

Guzzle: Silent HTTPS-Proxy Downgrade to Cleartext

CVSS 5.9 MEDIUMCWE-311CWE-319CWE-636
Em resumo

O cliente HTTP Guzzle pode enviar acidentalmente o tráfego do proxy em texto plano em vez de criptografado, expondo senhas e dados sensíveis ao usar proxies HTTPS com versões antigas do cURL. Isso acontece silenciosamente, sem aviso.

Detalhe técnico

CWE-311/319/636: Os manipuladores cURL do Guzzle aceitam URLs de proxy https://, mas libcurl <7.50.2 reduz silenciosamente para http:// não criptografado, transmitindo cabeçalhos Proxy-Authorization, credenciais de proxy e metadados de túnel CONNECT em texto plano. O vetor de ataque exige que a aplicação configure um proxy https:// com libcurl <7.50.2; o impacto inclui exposição de credenciais de proxy e divulgação de host/porta alvo no salto do proxy.

Resumo gerado e traduzido por IA a partir da descrição oficial.
Guzzle is an extensible PHP HTTP client. Prior to 7.12.1, in certain configurations, traffic expected to be protected by TLS on the hop to the proxy is transmitted in cleartext. Proxy authentication credentials (the Proxy-Authorization header, proxy userinfo in the proxy URL, or CURLOPT_PROXYUSERPWD) are sent without encryption, and the CONNECT target host and port for tunneled HTTPS requests are exposed. The built-in cURL handlers (GuzzleHttp\Handler\CurlHandler and GuzzleHttp\Handler\CurlMultiHandler, used by default whenever the PHP cURL extension is available) accept an https:// proxy. libcurl older than 7.50.2 silently treats an https:// proxy as a plaintext http:// proxy. The TLS connection to the proxy is never established, and the proxy leg is cleartext with no error or warning. An application is affected when it sends requests through one of the built-in cURL handlers, configures an https:// proxy expecting the proxy connection itself to be encrypted, and runs with libcurl older than 7.50.2. This vulnerability is fixed in 7.12.1.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Produtos afetados
guzzle · guzzle

Quer saber se a sua infraestrutura está exposta a isto?

Falar com a TrueHacking →