urllib3 before version 1.23 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.
https://github.com/urllib3/urllib3/pull/1346
https://github.com/urllib3/urllib3/issues/1316
https://github.com/urllib3/urllib3/blob/master/CHANGES.rst
https://bugzilla.redhat.com/show_bug.cgi?id=1649153
https://usn.ubuntu.com/3990-1/
https://access.redhat.com/errata/RHSA-2019:2272
http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00039.html
https://lists.debian.org/debian-lts-announce/2021/06/msg00015.html
Source: MITRE
Published: 2018-12-11
Updated: 2021-06-15
Type: NVD-CWE-noinfo
Base Score: 5
Vector: AV:N/AC:L/Au:N/C:P/I:N/A:N
Impact Score: 2.9
Exploitability Score: 10
Severity: MEDIUM
Base Score: 9.8
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Impact Score: 5.9
Exploitability Score: 3.9
Severity: CRITICAL