urllib3 before 1.24.2 does not remove the authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext. NOTE: this issue exists because of an incomplete fix for CVE-2018-20060 (which was case-sensitive).
{ "nvd_published_at": "2023-10-15T19:15:09Z", "cwe_ids": [ "CWE-200", "CWE-601" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2023-10-17T14:21:39Z" }