CVE-2022-31042highCWE-200

CVE-2022-31042: high-severity vulnerability in guzzle

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

Published · Updated

Follow this CVE+ Monitor guzzle+ Monitor mediawiki

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.5epss 2.0%
In short

Guzzle fails to remove sensitive Cookie headers when a website redirects to a different domain or from HTTPS to HTTP, potentially exposing authentication tokens and session data to untrusted servers.

Technical detail

When Guzzle follows HTTP redirects (3xx responses) to a different host or downgrades from HTTPS to HTTP, manually-set Cookie headers are not stripped before the redirect request, violating the same-origin policy. Only cookies managed by Guzzle's middleware were previously removed; the vulnerability affects manually-added headers. Attackers can trick applications into sending credentials to malicious domains via redirect chains.

Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
guzzle · guzzle
Related CVEs — guzzle

In the same product, most dangerous first.

CVE-2022-31043HIGHFix failure to strip Authorization header on HTTP downgrade in GuzzleEPSS 2.0%CVE-2022-31090HIGHCURLOPT_HTTPAUTH option not cleared on change of origin in GuzzleEPSS 1.9%CVE-2022-31091HIGHChange in port should be considered a change in origin in GuzzleEPSS 1.6%CVE-2022-29248HIGHCross-domain cookie leakage in GuzzleEPSS 1.4%CVE-2026-67353MEDIUMguzzlehttp/guzzle before 7.15.1 Unbounded Cookie Denial of ServiceEPSS 0.4%CVE-2026-67354HIGHguzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via RefererEPSS 0.4%