CVE-2022-31090
Published: 27 June 2022
Summary
CVE-2022-31090 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Guzzlephp Guzzle. Its CVSS base score is 7.7 (High).
Operationally, ranked in the top 16.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-5884
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 the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds…
more
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
The control's identification, isolation, alerting, and eradication steps directly limit the impact and exploitation window of unauthorized sensitive information exposure.
Proper media downgrading process prevents sensitive information from remaining on media that is then accessible to lower-classification recipients.
Policies requiring periodic review and deletion of inaccurate/outdated PII reduce the amount of sensitive information retained and therefore exposed.
Regular deletion of inaccurate or outdated PII directly reduces the volume of sensitive information retained that could be exposed.
De-identification directly prevents exposure of sensitive/PII data to unauthorized actors when datasets are released or shared.
Deleting information when no longer needed directly reduces the window during which sensitive data can be exposed to unauthorized actors.
Secure disposal techniques directly prevent sensitive data from becoming accessible to unauthorized actors after components leave organizational control.
Automated marking applies security attributes to system outputs, making it harder for attackers to exploit unmarked sensitive information leading to unauthorized exposure.