CVE-2021-28363: Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection

CVE-2021-28363 · Severity: low · CVSS 3.1 · Published 2021-03-15

The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.

Technologies: urllib3 (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2021-28363 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-28363 being exploited in the wild.
How severe is CVE-2021-28363?
Low severity, with a CVSS score of 3.1, published 15 March 2021.
Which products and versions are affected?
urllib3 (PyPI) ECOSYSTEM:introduced=1.26.0,fixed=1.26.4, GIT:introduced=0,fixed=8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0|ECOSYSTEM:introduced=1.26.0,fixed=1.26.4.
Is there a fix for CVE-2021-28363?
Yes. urllib3 (PyPI): upgrade to 1.26.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-28363?
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.26.4 or later
    pip install "urllib3>=1.26.4"

Affected products

  • urllib3 (PyPI) ECOSYSTEM:introduced=1.26.0,fixed=1.26.4, GIT:introduced=0,fixed=8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0|ECOSYSTEM:introduced=1.26.0,fixed=1.26.4

Identifiers

  • CVE-2021-28363
  • GHSA-5phf-pp7p-vc2r
  • PYSEC-2021-59

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