CVE-2022-29248 json
Cross-domain cookie leakage in Guzzle
published 2022-05-25 4 y ago modified 2026-09-19 50 d ago also BIT-drupal-2022-29248 , DRUPAL-CORE-2022-010 , EUVD-2022-3650 , GHSA-cwmx-hcrq-mhc3
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains 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. The 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. Guzzle versions 6.5.6 and 7.4.3 contain a patch for this issue. As a workaround, turn off the cookie middleware.
Patch / fix
- packagist guzzlehttp/guzzle 6.5.6, 7.4.3
- bitnami drupal 9.2.20, 9.3.14
- packagist drupal/core 9.2.20, 9.3.14
- guzzlephp guzzle 6.5.6, 7.4.3
- drupal drupal 9.2.20, 9.3.14
- guzzle Debian 14, Debian 13, Debian 12 7.4.4-1
- mediawiki Debian 14, Debian 13, Debian 12 1:1.35.7-1
debian advisories DEBIAN-CVE-2022-29248
- mediawiki Arch Linux 1.38.3-1
arch linux advisories AVG-2823
- github.com/guzzle/guzzle@74a8602 commit
- github.com/guzzle/guzzle#3018 pull request
- drupal.org/sa-core-2022-010 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-29248 updated cvss 8.0
php-guzzlehttp-guzzle: Cross-domain cookie leakage
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | guzzlehttp/guzzle | <6.5.6 >=7.0.0, <7.4.3 |
6.5.6 7.4.3 |
| bitnami | drupal | >=9.2.0, <9.2.20 >=9.3.0, <9.3.14 |
9.2.20 9.3.14 |
| packagist | drupal/core | >=8.0.0, <9.2.20 >=9.3.0, <9.3.14 |
9.2.20 9.3.14 |
Affected products
- guzzle guzzle
Classification
References
-
github.com
/guzzle/guzzle/pull/3018
web, issue-tracking, patch, third-party-advisory, advisory
-
github.com
/guzzle/guzzle/commit/74a8602c6faec9ef74b7a9391ac82c5e65b1cdab
web, patch, third-party-advisory, advisory
-
drupal.org
/sa-core-2022-010
web, patch, third-party-advisory, advisory
-
debian.org
/security/2022/dsa-5246
vendor-advisory, web, third-party-advisory, advisory
-
github.com
/guzzle/guzzle/security/advisories/GHSA-cwmx-hcrq-mhc3
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29248
advisory, web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/guzzlehttp/guzzle/CVE-2022-29248.yaml
web
-
github.com
/guzzle/guzzle
package
Sources
- CVE List CVE-2022-29248
- GitHub Advisory GHSA-cwmx-hcrq-mhc3
- NVD CVE-2022-29248
- OSV BIT-drupal-2022-29248
- OSV DRUPAL-CORE-2022-010
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.