Guzzle up to 6.5.7/7.4.1/7.4.4 Redirect information disclosure

Summaryinfo

A vulnerability was found in Guzzle up to 6.5.7/7.4.1/7.4.4 and classified as problematic. Affected is an unknown function of the component Redirect Handler. Such manipulation leads to information disclosure. This vulnerability is referenced as CVE-2022-31091. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Guzzle up to 6.5.7/7.4.1/7.4.4. It has been rated as problematic. Affected by this issue is an unknown code of the component Redirect Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:

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.

The weakness was published 06/28/2022 as GHSA-q559-8m2m-g699. The advisory is available at github.com. This vulnerability is handled as CVE-2022-31091 since 05/18/2022. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

Upgrading to version 6.5.8, 7.4.2 or 7.4.5 eliminates this vulnerability. Applying the patch 1dd98b0564cb3f6bd16ce683cb755f94c10fbd82 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Guzzle

Version

• 6.5.0
• 6.5.1
• 6.5.2
• 6.5.3
• 6.5.4
• 6.5.5
• 6.5.6
• 6.5.7
• 7.4.0
• 7.4.1
• 7.4.2
• 7.4.3
• 7.4.4

License

• open-source

Website

• Product: https://github.com/guzzle/guzzle/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion