CVE-2018-25091: Infoleak
First published: Sun Oct 15 2023(Updated: )
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 <a href="https://access.redhat.com/security/cve/CVE-2018-20060">CVE-2018-20060</a> (which was case-sensitive). <a href="https://github.com/urllib3/urllib3/compare/1.24.1...1.24.2">https://github.com/urllib3/urllib3/compare/1.24.1...1.24.2</a> <a href="https://github.com/urllib3/urllib3/issues/1510">https://github.com/urllib3/urllib3/issues/1510</a> <a href="https://github.com/urllib3/urllib3/commit/adb358f8e06865406d1f05e581a16cbea2136fbc">https://github.com/urllib3/urllib3/commit/adb358f8e06865406d1f05e581a16cbea2136fbc</a>
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Python urllib3 | <1.24.2 | |
| pip/urllib3 | <1.24.2 | 1.24.2 |
| redhat/urllib3 | <1.24.2 | 1.24.2 |
| <1.24.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2018-25091
- https://github.com/urllib3/urllib3/issues/1510
- https://github.com/urllib3/urllib3/commit/adb358f8e06865406d1f05e581a16cbea2136fbc
- https://github.com/urllib3/urllib3/compare/1.24.1...1.24.2
- https://github.com/pypa/advisory-database/tree/main/vulns/urllib3/PYSEC-2023-207.yaml
- https://github.com/advisories/GHSA-gwvm-45gx-3cf8 (Advisory)
- https://access.redhat.com/security/cve/CVE-2018-20060
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246497
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246498
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246490
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246491
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246520
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246492
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246500
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246501
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246502
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246503
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246504
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246505
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246506
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246507
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246493
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246519
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246508
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246509
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246494
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246510
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246511
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246513
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246514
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246515
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246495
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246489
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246521
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246516
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246496
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246517
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2246518
- https://access.redhat.com/errata/RHSA-2024:2988
- https://bugzilla.redhat.com/show_bug.cgi?id=2244340
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).
- collector/nvd-api
- collector/nvd-index
- collector/github-advisory
- alias/GHSA-gwvm-45gx-3cf8
- alias/CVE-2018-25091
- agent/type
- agent/weakness
- agent/severity
- agent/remedy
- agent/author
- agent/softwarecombine
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- agent/software-canonical-lookup
- agent/references
- agent/event
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- collector/github-advisory-latest
- source/GitHub
- agent/last-modified-date
- collector/nvd-cve
- source/NVD
- agent/tags
- vendor/python
- canonical/python urllib3
- package-manager/pip
- package-manager/redhat