CVE-2022-29248

Cross-domain cookie leakage in Guzzle

Workarounds

If you do not need support for cookies, turn off the cookie middleware. It is already off by default, but if you have turned it on and no longer need it, turn it off.

References

• RFC6265 Section 5.3
• 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.

Previous version of Guzzle contain a vulnerability with the cookie middleware. The vulnerability is that it is not checked if the cookie domain equals the domain of the server which sets the cookie via the Set-Cookie header, allowing a malicious server to set cookies for unrelated domains. For example an attacker at www.example.com might set a session cookie for api.example.net, logging the Guzzle client into their account and retrieving private API requests from the security log of their account.

Note that our cookie middleware is disabled by default, so most library consumers will not be affected by this issue. Only those who manually add the cookie middleware to the handler stack or construct the client with ['cookies' => true] are affected. Moreover, those who do not use the same Guzzle client to call multiple domains and have disabled redirect forwarding are not affected by this vulnerability.

CVE-2022-29248 has a CVSS score of 8.0 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.5.6, 7.4.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Affected Guzzle 7 users should upgrade to Guzzle 7.4.3 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.6 or 7.4.3.

1. What is CVE-2022-29248? CVE-2022-29248 is a high-severity security vulnerability in guzzlehttp/guzzle (composer), affecting versions < 6.5.6. It is fixed in 6.5.6, 7.4.3.
2. How severe is CVE-2022-29248? CVE-2022-29248 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of guzzlehttp/guzzle are affected by CVE-2022-29248? guzzlehttp/guzzle (composer) versions < 6.5.6 is affected.
4. Is there a fix for CVE-2022-29248? Yes. CVE-2022-29248 is fixed in 6.5.6, 7.4.3. Upgrade to this version or later.
5. Is CVE-2022-29248 exploitable, and should I be worried? Whether CVE-2022-29248 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-29248 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-29248?
   • Upgrade guzzlehttp/guzzle to 6.5.6 or later
   • Upgrade guzzlehttp/guzzle to 7.4.3 or later

Other vulnerabilities in guzzlehttp/guzzle