8.1
CWE
565 200
Advisory Published
CVE Published
Updated

CVE-2022-29248: Infoleak

First published: Wed May 25 2022(Updated: )

### Impact 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. ### Patches 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. ### 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](https://datatracker.ietf.org/doc/html/rfc6265#section-5.3) * [RFC9110 Section 15.4](https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx) ### 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](https://php-http.slack.com/). Do not report additional security advisories in that public channel, however - please follow our [vulnerability reporting process](https://github.com/guzzle/guzzle/security/policy).

Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Guzzlephp Guzzle<6.5.6
Guzzlephp Guzzle>=7.0.0<7.4.3
Drupal Drupal>=9.2.0<9.2.20
Drupal Drupal>=9.3.0<9.3.14
Debian Debian Linux=11.0
composer/guzzlehttp/guzzle>=7<7.4.3>=4<6.5.6
debian/guzzle
7.4.5-1
debian/mediawiki
1:1.31.16-1+deb10u2
1:1.31.16-1+deb10u6
1:1.35.11-1~deb11u1
1:1.35.13-1~deb11u1
1:1.39.4-1~deb12u1
1:1.39.5-1~deb12u1
1:1.39.5-1
composer/guzzlehttp/guzzle>=7.0.0<7.4.3
7.4.3
composer/guzzlehttp/guzzle<6.5.6
6.5.6
<6.5.6
>=7.0.0<7.4.3
>=9.2.0<9.2.20
>=9.3.0<9.3.14
=11.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the vulnerability ID for this issue?

    The vulnerability ID for this issue is CVE-2022-29248.

  • What is the impact of this vulnerability?

    The impact of this vulnerability is cross-domain cookie leakage, allowing a malicious server to set cookies for unrelated domains.

  • Which software versions are affected by this vulnerability?

    The affected software versions include Guzzlephp Guzzle up to version 6.5.6, Guzzlephp Guzzle versions between 7.0.0 and 7.4.3, Drupal Drupal versions between 9.2.0 and 9.2.20, Drupal Drupal versions between 9.3.0 and 9.3.14, and Debian Debian Linux version 11.0.

  • What is the severity level of this vulnerability?

    The severity level of this vulnerability is high, with a severity value of 8.1.

  • How can I fix this vulnerability?

    To fix this vulnerability, you should update to Guzzle version 7.4.3 or higher, Drupal version 9.2.21 or higher, Drupal version 9.3.15 or higher, or Debian Debian Linux version 11.1 or higher.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203