Bug 2129255 (CVE-2022-29248) - CVE-2022-29248 php-guzzlehttp-guzzle: Cross-domain cookie leakage
Summary: CVE-2022-29248 php-guzzlehttp-guzzle: Cross-domain cookie leakage
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-29248
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2129256 2129257
Blocks: 2126823
TreeView+ depends on / blocked
 
Reported: 2022-09-23 05:58 UTC by Avinash Hanwate
Modified: 2022-11-28 00:27 UTC (History)
1 user (show)

Fixed In Version: php-guzzlehttp-guzzle 6.5.6, php-guzzlehttp-guzzle 7.4.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-28 00:27:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2022-09-23 05:58:17 UTC
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.

Comment 1 Avinash Hanwate 2022-09-23 05:58:42 UTC
Created php-guzzlehttp-guzzle tracking bugs for this issue:

Affects: epel-all [bug 2129256]
Affects: fedora-all [bug 2129257]

Comment 2 Product Security DevOps Team 2022-11-28 00:26:58 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.