CVE-2018-20060: Exposure of Sensitive Information to an Unauthorized Actor in urllib3

CVE-2018-20060 · Severity: low · CVSS 3 · Published 2018-12-11

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.

Technologies: urllib3 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2018-20060 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-20060 being exploited in the wild.
How severe is CVE-2018-20060?
Low severity, with a CVSS score of 3, published 11 December 2018.
Which products and versions are affected?
urllib3 (PyPI) ECOSYSTEM:introduced=0,fixed=1.23.
Is there a fix for CVE-2018-20060?
Yes. urllib3 (PyPI): upgrade to 1.23 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-20060?
Check whether you run urllib3 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • urllib3 (PyPI): upgrade to 1.23 or later
    pip install "urllib3>=1.23"

Affected products

  • urllib3 (PyPI) ECOSYSTEM:introduced=0,fixed=1.23

Identifiers

  • CVE-2018-20060
  • GHSA-www2-v7xj-xrc6
  • PYSEC-2018-32

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.