CVE-2022-31091
Guzzlephp Guzzle vulnerability
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.
Affected products
Guzzle, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Guzzlephp Guzzle runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 · Patch
- github.com/guzzle/guzzle/security/advisories/GHSA-q559-8m2m-g699 · Mitigation
- www.debian.org/security/2022/dsa-5246 · Third Party Advisory
- security.gentoo.org/glsa/202305-24
- nvd.nist.gov/vuln/detail/CVE-2022-31091
- cve.org/CVERecord?id=CVE-2022-31091
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.