Vulnerability advisory

GHSA-w248-ffj2-4v5q

Fix failure to strip Authorization header on HTTP downgrade

Published Jun 9, 2022Updated Dec 10, 2025OSV record ↗

Also known as BIT-drupal-2022-31042BIT-drupal-2022-31043CVE-2022-31042CVE-2022-31043DRUPAL-CORE-2022-011GHSA-f2wf-25xc-69c9

Severity

CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected versions

guzzlehttp/guzzle Packagist

All guzzlehttp/guzzle advisories →

Affected	Fixed in
`4.0.0` to before 6.5.7	`6.5.7`Advisories →
Also listed as affected (50) `4.0.0` `4.0.1` `4.0.2` `4.1.0` `4.1.1` `4.1.2` `4.1.3` `4.1.4` `4.1.5` `4.1.6` `4.1.7` `4.1.8` `4.2.0` `4.2.1` `4.2.2` `4.2.3` `4.2.4` `5.0.0` `5.0.1` `5.0.2` `5.0.3` `5.1.0` `5.2.0` `5.3.0` `5.3.1` `5.3.2` `5.3.3` `5.3.4` `6.0.0` `6.0.1` `6.0.2` `6.1.0` `6.1.1` `6.2.0` `6.2.1` `6.2.2` `6.2.3` `6.3.0` `6.3.1` `6.3.2` `6.3.3` `6.4.0` `6.4.1` `6.5.0` `6.5.1` `6.5.2` `6.5.3` `6.5.4` `6.5.5` `6.5.6`
`7.0.0` to before 7.4.4	`7.4.4`Advisories →
Also listed as affected (10) `7.0.0` `7.0.1` `7.1.0` `7.1.1` `7.2.0` `7.3.0` `7.4.0` `7.4.1` `7.4.2` `7.4.3`

Description

Impact

Authorization headers on requests are sensitive information. On making a request using the https scheme to a server which responds with a redirect to a URI with the http scheme, we should not forward the Authorization header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, https to http downgrades did not result in the Authorization header being removed, only changes to the host.

Patches

Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.

Workarounds

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.

References

RFC9110 Section 15.4

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. Do not report additional security advisories in that public channel, however - please follow our vulnerability reporting process.