You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
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.
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.
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. 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. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.
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. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach which would be to use their own redirect middleware. Alternately users may simply disable redirects all together if redirects are not expected or required.
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. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.
guzzlehttp/psr7 is a PSR-7 HTTP message library. Versions prior to 1.8.4 and 2.1.1 are vulnerable to improper header parsing. An attacker could sneak in a new line character and pass untrusted values. The issue is patched in 1.8.4 and 2.1.1. There are currently no known workarounds.
mend-for-github-combot
changed the title
guzzlehttp/guzzle-6.3.3: 6 vulnerabilities (highest severity is: 8.1)
guzzlehttp/guzzle-6.3.3: 1 vulnerabilities (highest severity is: 8.1)
Jan 8, 2023
mend-for-github-combot
changed the title
guzzlehttp/guzzle-6.3.3: 1 vulnerabilities (highest severity is: 8.1)
guzzlehttp/guzzle-6.3.3: 2 vulnerabilities (highest severity is: 8.1)
Oct 12, 2023
mend-for-github-combot
changed the title
guzzlehttp/guzzle-6.3.3: 2 vulnerabilities (highest severity is: 8.1)
guzzlehttp/guzzle-6.3.3: 6 vulnerabilities (highest severity is: 8.1)
Mar 6, 2024
mend-for-github-combot
changed the title
guzzlehttp/guzzle-6.3.3: 6 vulnerabilities (highest severity is: 8.1)
guzzlehttp/guzzle-6.3.3: 6 vulnerabilities (highest severity is: 8.0)
Sep 8, 2024
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2022-29248
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2022-05-25
URL: CVE-2022-29248
CVSS 3 Score Details (8.0)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29248
Release Date: 2022-05-25
Fix Resolution: guzzlehttp/guzzle - 6.5.6,guzzlehttp/guzzle - 7.4.3
CVE-2022-31091
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
Guzzle, an extensible PHP HTTP client.
Authorization
andCookie
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 theAuthorization
andCookie
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.Publish Date: 2022-06-27
URL: CVE-2022-31091
CVSS 3 Score Details (7.7)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31091
Release Date: 2022-06-27
Fix Resolution: 6.5.8,7.4.5
CVE-2022-31090
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
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 theCURLOPT_HTTPAUTH
option to specify anAuthorization
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 theCURLOPT_HTTPAUTH
option before continuing, stopping curl from appending theAuthorization
header to the new request. 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. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.Publish Date: 2022-06-27
URL: CVE-2022-31090
CVSS 3 Score Details (7.7)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-25mq-v84q-4j7r
Release Date: 2022-05-19
Fix Resolution: 6.5.8,7.4.5
CVE-2022-31043
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
Guzzle is an open source PHP HTTP client. In affected versions
Authorization
headers on requests are sensitive information. On making a request using thehttps
scheme to a server which responds with a redirect to a URI with thehttp
scheme, we should not forward theAuthorization
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
tohttp
downgrades did not result in theAuthorization
header being removed, only changes to the host. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach which would be to use their own redirect middleware. Alternately users may simply disable redirects all together if redirects are not expected or required.Publish Date: 2022-06-09
URL: CVE-2022-31043
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-w248-ffj2-4v5q
Release Date: 2022-06-10
Fix Resolution: 6.5.7,7.4.4
CVE-2022-31042
Vulnerable Library - guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
Guzzle is an open source PHP HTTP client. In affected versions the
Cookie
headers on requests are sensitive information. On making a request using thehttps
scheme to a server which responds with a redirect to a URI with thehttp
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 theCookie
header on. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and anyCookie
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. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. If you do not require or expect redirects to be followed, one should simply disable redirects all together.Publish Date: 2022-06-09
URL: CVE-2022-31042
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-f2wf-25xc-69c9
Release Date: 2022-06-10
Fix Resolution: 6.5.7,7.4.4
CVE-2022-24775
Vulnerable Library - guzzlehttp/psr7-1.6.1
PSR-7 HTTP message library
Dependency Hierarchy:
Found in HEAD commit: 0dfef3330db7c4b7991066ad624f6659c0ffe46a
Found in base branch: main
Vulnerability Details
guzzlehttp/psr7 is a PSR-7 HTTP message library. Versions prior to 1.8.4 and 2.1.1 are vulnerable to improper header parsing. An attacker could sneak in a new line character and pass untrusted values. The issue is patched in 1.8.4 and 2.1.1. There are currently no known workarounds.
Publish Date: 2022-03-21
URL: CVE-2022-24775
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-q7rv-6hp3-vh96
Release Date: 2022-03-21
Fix Resolution: 1.8.4,2.1.1
The text was updated successfully, but these errors were encountered: