CVSS: 7.7EPSS: 0%CPEs: 3EXPL: 0CVE-2022-31091 – Change in port should be considered a change in origin in Guzzle
https://notcve.org/view.php?id=CVE-2022-31091
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. • https://github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 https://github.com/guzzle/guzzle/security/advisories/GHSA-q559-8m2m-g699 https://security.gentoo.org/glsa/202305-24 https://www.debian.org/security/2022/dsa-5246 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.7EPSS: 0%CPEs: 3EXPL: 0CVE-2022-31090 – CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle
https://notcve.org/view.php?id=CVE-2022-31090
Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. • https://github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 https://github.com/guzzle/guzzle/security/advisories/GHSA-25mq-v84q-4j7r https://security.gentoo.org/glsa/202305-24 https://www.debian.org/security/2022/dsa-5246 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer •
CVSS: 7.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-31043 – Fix failure to strip Authorization header on HTTP downgrade in Guzzle
https://notcve.org/view.php?id=CVE-2022-31043
Guzzle is an open source PHP HTTP client. In affected versions `Authorization` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, `https` to `http` downgrades did not result in the `Authorization` header being removed, only changes to the host. • https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8 https://github.com/guzzle/guzzle/security/advisories/GHSA-w248-ffj2-4v5q https://www.debian.org/security/2022/dsa-5246 https://www.drupal.org/sa-core-2022-011 https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer •
CVSS: 7.5EPSS: 0%CPEs: 8EXPL: 0CVE-2022-31042 – Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle
https://notcve.org/view.php?id=CVE-2022-31042
Guzzle is an open source PHP HTTP client. In affected versions the `Cookie` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. • https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8 https://github.com/guzzle/guzzle/security/advisories/GHSA-f2wf-25xc-69c9 https://www.debian.org/security/2022/dsa-5246 https://www.drupal.org/sa-core-2022-011 https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer •
CVSS: 8.1EPSS: 0%CPEs: 5EXPL: 0CVE-2022-29248 – Cross-domain cookie leakage in Guzzle
https://notcve.org/view.php?id=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 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. • https://github.com/guzzle/guzzle/commit/74a8602c6faec9ef74b7a9391ac82c5e65b1cdab https://github.com/guzzle/guzzle/pull/3018 https://github.com/guzzle/guzzle/security/advisories/GHSA-cwmx-hcrq-mhc3 https://www.debian.org/security/2022/dsa-5246 https://www.drupal.org/sa-core-2022-010 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-565: Reliance on Cookies without Validation and Integrity Checking •