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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
| Link | Tags |
|---|---|
| https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8 | third party advisory patch |
| https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xx | third party advisory |
| https://github.com/guzzle/guzzle/security/advisories/GHSA-w248-ffj2-4v5q | third party advisory |
| https://www.drupal.org/sa-core-2022-011 | third party advisory patch |
| https://www.debian.org/security/2022/dsa-5246 | third party advisory vendor advisory |