Vulnerability advisory
CVE-2022-31091
Change in port should be considered a change in origin in Guzzle
Also known as GHSA-q559-8m2m-g699
- CVSS 3.x
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/guzzle/guzzle ↗ | |
| All commits before a52f0440530b54fa079ce76e8c5d196a42cad981 | a52f0440530b54fa079ce76e8c5d196a42cad981 |
| 414c24961042f6616fb43e23fa69a785f9fc053e to before 1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 | 1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 |
Also listed as affected (130)
| |
Description
Guzzle, an extensible PHP HTTP client. Authorization and Cookie headers on requests are sensitive information. In affected versions on making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the Authorization and Cookie headers from the request, before containing. Previously, we would only consider a change in host or scheme. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.
References
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2022/31xxx/CVE-2022-31091.json ↗
- Advisorygithub.com/guzzle/guzzle/security/advisories/GHSA-q559-8m2m-g699 ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-31091 ↗
- Advisorysecurity.gentoo.org/glsa/202305-24 ↗
- Advisorywww.debian.org/security/2022/dsa-5246 ↗
- Fixgithub.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 ↗