Closed mend-bolt-for-github[bot] closed 1 year ago
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
CVE-2022-31042 - High Severity Vulnerability
Vulnerable Libraries - guzzlehttp/guzzle-6.3.3, guzzlehttp/guzzle-6.3.0
guzzlehttp/guzzle-6.3.3
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy: - :x: **guzzlehttp/guzzle-6.3.3** (Vulnerable Library)
guzzlehttp/guzzle-6.3.0
Guzzle, an extensible PHP HTTP client
Dependency Hierarchy: - google/apiclient-v2.2.1 (Root Library) - :x: **guzzlehttp/guzzle-6.3.0** (Vulnerable Library)
Found in HEAD commit: ab76dd905220f63a5e50d7a6c36543f1d876d52a
Found in base branch: master
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 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.
Publish Date: 2022-06-10
URL: CVE-2022-31042
CVSS 3 Score Details (7.5)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/guzzle/guzzle/security/advisories/GHSA-f2wf-25xc-69c9
Release Date: 2022-06-10
Fix Resolution: 6.5.7,7.4.4
Step up your Open Source Security Game with Mend here