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 product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Guzzle | Guzzlephp | * | 6.5.8 (excluding) |
| Guzzle | Guzzlephp | 7.0.0 (including) | 7.4.5 (excluding) |
| Civicrm | Ubuntu | bionic | * |
| Civicrm | Ubuntu | impish | * |
| Civicrm | Ubuntu | kinetic | * |
| Civicrm | Ubuntu | xenial | * |
| Guzzle | Ubuntu | kinetic | * |
| Guzzle | Ubuntu | upstream | * |
| Icinga-php-thirdparty | Ubuntu | kinetic | * |
| Icinga-php-thirdparty | Ubuntu | lunar | * |
| Icinga-php-thirdparty | Ubuntu | mantic | * |
| Icingaweb2-module-reactbundle | Ubuntu | impish | * |
| Icingaweb2-module-reactbundle | Ubuntu | kinetic | * |
| Icingaweb2-module-reactbundle | Ubuntu | lunar | * |
| Icingaweb2-module-reactbundle | Ubuntu | mantic | * |
| Mediawiki | Ubuntu | bionic | * |
| Mediawiki | Ubuntu | impish | * |
| Mediawiki | Ubuntu | trusty | * |
| Mediawiki | Ubuntu | upstream | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.