CVE-2018-25091: Infoleak
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).
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2018-25091?
The severity of CVE-2018-25091 is medium.
How does CVE-2018-25091 affect urllib3 before version 1.24.2?
CVE-2018-25091 allows for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext.
How can I fix CVE-2018-25091 in urllib3?
To fix CVE-2018-25091, you need to upgrade urllib3 to version 1.24.2 or higher.
Where can I find more information about CVE-2018-25091?
You can find more information about CVE-2018-25091 at the following links: [NIST NVD](https://nvd.nist.gov/vuln/detail/CVE-2018-25091), [GitHub Issue](https://github.com/urllib3/urllib3/issues/1510), [GitHub Commit](https://github.com/urllib3/urllib3/commit/adb358f8e06865406d1f05e581a16cbea2136fbc).