CVE-2022-29248: Cross-domain cookie leakage in Guzzle

CVE-2022-29248 · Severity: low · CVSS 3.1 · Published 2022-05-25

Cross-domain cookie leakage in Guzzle

Technologies: drupal/core (Packagist), guzzlehttp/guzzle (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2022-29248 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-29248 being exploited in the wild.
How severe is CVE-2022-29248?
Low severity, with a CVSS score of 3.1, published 25 May 2022.
Which products and versions are affected?
drupal/core (Packagist) ECOSYSTEM:introduced=8.0.0,fixed=9.2.20|ECOSYSTEM:introduced=9.3.0,fixed=9.3.14; guzzlehttp/guzzle (Packagist) ECOSYSTEM:introduced=0,fixed=6.5.6.
Is there a fix for CVE-2022-29248?
Yes. drupal/core (Packagist): upgrade to 9.2.20 or later; guzzlehttp/guzzle (Packagist): upgrade to 6.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-29248?
Check whether you run drupal/core (Packagist) or guzzlehttp/guzzle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • drupal/core (Packagist): upgrade to 9.2.20 or later
    composer require drupal/core:^9.2.20
  • guzzlehttp/guzzle (Packagist): upgrade to 6.5.6 or later
    composer require guzzlehttp/guzzle:^6.5.6

Affected products

  • drupal/core (Packagist) ECOSYSTEM:introduced=8.0.0,fixed=9.2.20|ECOSYSTEM:introduced=9.3.0,fixed=9.3.14
  • guzzlehttp/guzzle (Packagist) ECOSYSTEM:introduced=0,fixed=6.5.6

Identifiers

  • CVE-2022-29248
  • DRUPAL-CORE-2022-010
  • GHSA-cwmx-hcrq-mhc3

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.