Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle
Summary
Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2022-31042 guzzle Fixed in: 7.4.4-1
- Ubuntu UBUNTU-CVE-2022-31042 guzzle
References
- advisory github.com
- advisory debian.org
- advisory nvd.nist.gov
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- patch github.com
- web drupal.org
- web rfc-editor.org