CVE-2022-31090
CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle
En resumen
El manejador Curl de Guzzle no elimina los encabezados de Autorización al seguir redirecciones a un sitio diferente (host, puerto o protocolo diferentes). Esto permite que las credenciales sensibles se filtren a destinos no deseados.
Detalle técnico
Cuando el manejador Curl de Guzzle sigue redirecciones HTTP mediante CURLOPT_HTTPAUTH, el encabezado Authorization no se elimina al cambiar de origen (host, esquema o puerto). Un atacante que controla un servidor objetivo legítimo puede redirigir solicitudes autenticadas a un servidor tercero malicioso, exponiendo credenciales. Precondición: la aplicación debe seguir redirecciones y utilizar el manejador Curl con CURLOPT_HTTPAUTH.
Resumen generado y traducido por IA a partir de la descripción oficial.
Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Productos afectados
guzzle · guzzle¿Quieres saber si tu infraestructura está expuesta a esto?
Hablar con TrueHacking →