GHSA-f2wf-25xc-69c9 Failure to strip the Cookie header on change in host or HTTP downgrade

• Packagist guzzlehttp/guzzle: >= 4.0.0, < 6.5.7 → fixed in 6.5.7 • Packagist guzzlehttp/guzzle: >= 7.0.0, < 7.4.4 → fixed in 7.4.4

Impact `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. 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.