CVE-2022-31091
Change in port should be considered a change in origin in Guzzle
In short
Guzzle PHP HTTP client fails to remove sensitive Authorization and Cookie headers when automatically following redirects to URLs with different ports. This allows credentials to leak to unintended destinations.
Technical detail
CWE-200 information exposure vulnerability in Guzzle's redirect handling: when following HTTP redirects, the library only checked for changes in host and scheme, but not port number, resulting in sensitive Authorization and Cookie headers being forwarded across origin boundaries. Attack requires server-side redirect to different port; requires application to follow redirects automatically (default behavior).
Summary generated and translated by AI from the official description.
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
Affected products
guzzle · guzzleWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →