7.7
CWE
200 212
Advisory Published
CVE Published
Updated

CVE-2022-31090: CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle

First published: Mon Jun 20 2022(Updated: )

### Impact `Authorization` headers on requests are sensitive information. 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, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin. ### Patches 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. ### Workarounds 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 stream handler backend, rather than curl. ### References * [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx) * [CVE-2022-27776](https://curl.se/docs/CVE-2022-27776.html) ### For more information If you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the [PHP HTTP Slack](https://php-http.slack.com/). Do not report additional security advisories in that public channel, however - please follow our [vulnerability reporting process](https://github.com/guzzle/guzzle/security/policy).

Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
composer/guzzlehttp/guzzle>=7<7.4.5>=4<6.5.8
composer/guzzlehttp/guzzle>=7.0.0<7.4.5
7.4.5
composer/guzzlehttp/guzzle<6.5.8
6.5.8
debian/guzzle
7.4.5-1
debian/mediawiki
1:1.31.16-1+deb10u2
1:1.31.16-1+deb10u6
1:1.35.11-1~deb11u1
1:1.35.13-1~deb11u1
1:1.39.4-1~deb12u1
1:1.39.5-1~deb12u1
1:1.39.5-1
guzzlephp Guzzle<6.5.8
guzzlephp Guzzle>=7.0.0<7.4.5
Debian Debian Linux=11.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the vulnerability ID?

    The vulnerability ID is CVE-2022-31090.

  • What is the impact of the vulnerability?

    The impact of the vulnerability is sensitive information exposure.

  • Which software versions are affected by this vulnerability?

    The software versions affected are Guzzlephp Guzzle up to version 6.5.8, Guzzlephp Guzzle versions between 7.0.0 and 7.4.5, and Debian Debian Linux version 11.0.

  • How severe is the vulnerability?

    The vulnerability has a severity score of 7.7 (high).

  • How can I fix the vulnerability?

    To fix the vulnerability, update to Guzzlephp Guzzle version 7.4.5 or later, or apply the appropriate security patches for Debian Debian Linux version 11.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203