CVE-2022-31042: Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle
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.
Other sources
Failure to strip the Cookie header on change in host or HTTP downgrade
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the impact of CVE-2022-31042?
`Cookie` headers on requests are sensitive information and can be exposed when making certain types of requests.
What software packages are affected by CVE-2022-31042?
Packages such as Guzzle, MediaWiki, Drupal, and Debian Linux are affected.
What is the severity level of CVE-2022-31042?
The severity level of CVE-2022-31042 is high (7).
How can I fix CVE-2022-31042?
To fix CVE-2022-31042, it is recommended to update the affected software packages to the specified versions.
Where can I find more information about CVE-2022-31042?
More information about CVE-2022-31042 can be found at the provided references.