Exposure of Sensitive Information to an Unauthorized Actor in urllib3
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-20060US | critical9.8 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00039.htmlWEB
- https://access.redhat.com/errata/RHSA-2019:2272WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=1649153WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/urllib3/PYSEC-2018-32.yamlWEB
- https://github.com/urllib3/urllib3PACKAGE
- https://github.com/urllib3/urllib3/blob/master/CHANGES.rstWEB
- https://github.com/urllib3/urllib3/commit/560bd227b90f74417ffaedebf5f8d05a8ee4f532WEB
- https://github.com/urllib3/urllib3/issues/1316WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan