CVE-2022-31091

guzzle: Guzzle, an extensible PHP HTTP client

CVE-2022-31091 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2022-31091, released June 27, 2022. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.7
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0157
75th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
guzzle · Debian 12.15 (bookworm) 7.4.5-1 DEBIAN-CVE-2022-31091 Jun 27, 2022
guzzle · Debian 13.5 (trixie) 7.4.5-1 DEBIAN-CVE-2022-31091 Jun 27, 2022
guzzle · Debian 14 7.4.5-1 DEBIAN-CVE-2022-31091 Jun 27, 2022
mediawiki · Debian 12.15 (bookworm) 1:1.35.7-1 DEBIAN-CVE-2022-31091 Jun 27, 2022
mediawiki · Debian 13.5 (trixie) 1:1.35.7-1 DEBIAN-CVE-2022-31091 Jun 27, 2022
mediawiki · Debian 14 1:1.35.7-1 DEBIAN-CVE-2022-31091 Jun 27, 2022

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.