CVE-2022-31091
Change in port should be considered a change in origin in Guzzle
En resumen
La librería Guzzle de PHP no elimina encabezados sensibles de autorización al seguir redirecciones a URLs con puertos diferentes. Esto causa exposición de credenciales a destinos no autorizados.
Detalle técnico
Vulnerabilidad CWE-200 en el manejo de redirecciones de Guzzle: la librería omite la eliminación de encabezados Authorization y Cookie al seguir redirecciones HTTP hacia destinos con puerto diferente, aunque host y scheme sean idénticos. El ataque requiere un servidor que responda con redirección a puerto diferente; depende de que la aplicación siga redirecciones automáticamente.
Resumen generado y traducido por IA a partir de la descripción oficial.
Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` headers on requests are sensitive information. In affected versions on making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme. 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. An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.
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 →