CVE-2022-29248 — Sensitive Information Exposure

Vendor	Product	Version range	Fixed in
debian	debian_linux	—	—
debian	guzzle	< guzzle 7.4.4-1 (bookworm)	guzzle 7.4.4-1 (bookworm)
debian	mediawiki	< guzzle 7.4.4-1 (bookworm)	guzzle 7.4.4-1 (bookworm)
drupal	core	>= 8.0.0 < 9.2.20	9.2.20
drupal	core	>= 9.3.0 < 9.3.14	9.3.14
drupal	drupal	>= 9.2.0 < 9.2.20	9.2.20
drupal	drupal	>= 9.3.0 < 9.3.14	9.3.14
drupal	drupal_core	—	—
guzzle	guzzle	< 6.5.6	6.5.6
guzzle	guzzle	—	—
guzzle	guzzle	>= 0 < 7.4.4-1	7.4.4-1
guzzle	guzzle	>= 0 < 7.4.4-1	7.4.4-1
guzzle	guzzle	>= 0 < 7.4.4-1	7.4.4-1
guzzlehttp	guzzle	>= 0 < 6.5.6	6.5.6
guzzlehttp	guzzle	>= 7.0.0 < 7.4.3	7.4.3
guzzlephp	guzzle	< 6.5.6	6.5.6
guzzlephp	guzzle	>= 7.0.0 < 7.4.3	7.4.3
mediawiki	mediawiki	>= 0 < 1:1.35.8-1~deb11u1	1:1.35.8-1~deb11u1
mediawiki	mediawiki	>= 0 < 1:1.35.7-1	1:1.35.7-1
mediawiki	mediawiki	>= 0 < 1:1.35.7-1	1:1.35.7-1
mediawiki	mediawiki	>= 0 < 1:1.35.7-1	1:1.35.7-1

OSV

Cross-domain cookie leakage in Guzzle

osv·2022-05-25

CVE-2022-29248 [HIGH] Cross-domain cookie leakage in Guzzle Cross-domain cookie leakage in Guzzle ### 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]`

OSV

CVE-2022-29248: Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services

osv·2022-05-25

CVE-2022-29248 CVE-2022-29248: Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. [Guzzle has released a security update](https://github.com/guzzle/guzzle/security/advisories/GHSA-cwmx-hcrq-mhc3) which does not affect Drupal core, but may affect some contributed projects or custom code on Drupal sites. We are issuing this security advisory outside our regular [Drupal security release window schedule](https://www.drupal.org/node/1173280) since Guzzle has already published information about the vulnerability, and vulnerabilities might exist in contributed modules or custom modules that use Guzzle for outgoing requests. Guzzle has rated this vulnerability as high-risk. This advisory is not covered by Drupal Steward.

GHSA

Cross-domain cookie leakage in Guzzle

ghsa·2022-05-25

CVE-2022-29248 [HIGH] CWE-200 Cross-domain cookie leakage in Guzzle Cross-domain cookie leakage in Guzzle ### 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]`

OSV

CVE-2022-29248: Guzzle is a PHP HTTP client

osv·2022-05-25·CVSS 8.1

CVE-2022-29248 [HIGH] CVE-2022-29248: Guzzle is a PHP HTTP client 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

Drupal

Drupal core - Moderately critical - Third-party libraries - SA-CORE-2022-010

vendor_drupal·2022-05-25

CVE-2022-29248 [MEDIUM] Drupal core - Moderately critical - Third-party libraries - SA-CORE-2022-010 Title: Drupal core - Moderately critical - Third-party libraries - SA-CORE-2022-010 Vulnerability Type: Third-party libraries Description: Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. Guzzle has released a security update which does not affect Drupal core, but may affect some contributed projects or custom code on Drupal sites. We are issuing this security advisory outside our regular Drupal security release window schedule since Guzzle has already published information about the vulnerability, and vulnerabilities might exist in contributed modules or custom modules that use Guzzle for outgoing requests. Guzzle has rated this vulnerability as high-risk. This advisory is not covered by Drupal Steward. Solution: Install the late

Debian

CVE-2022-29248: guzzle - Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains a...

vendor_debian·2022·CVSS 8.0

CVE-2022-29248 [HIGH] CVE-2022-29248: guzzle - Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains a... 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

CVE-2022-29248: 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…

Affected

CVSS provenance