Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle

Summary

Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` 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, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. 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. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

Timeline

1. Jun 9, 2022, 12:00 AM UTCCVE published
2. Apr 23, 2025, 3:54 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Apr 23, 2025, 6:18 PM UTCRecord last updated

Affected versions

• guzzle guzzle

  fixed in 6.5.7; From 7.0.0 · fixed in 7.4.4

• guzzlehttp/guzzlePackagist

  From 4.0.0 · fixed in 6.5.7

• guzzlehttp/guzzlePackagist

  From 7.0.0 · fixed in 7.4.4

• drupal/corePackagist

  From 8.0.0 · fixed in 9.2.21; From 9.3.0 · fixed in 9.3.16

References 5