NetSight
medium6.5

CVE-2021-28363

Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection

Impact

### Impact Users who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`. Only the default SSLContext is impacted. ### Patches [urllib3 >=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3<1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies. ### Workarounds Upgrading is recommended as this is a minor release and not likely to break current usage. Configuring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext` ### For more information If you have any questions or comments about this advisory: * Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)

Affected packages

EcosystemPackageAffectedFixed in
pipurllib3>= 1.26.0, < 1.26.41.26.4

Affected products

VendorProductAffected versions
PythonUrllib3
from 1.26.0 before 1.26.4
FedoraprojectFedora
Version 34
OraclePeoplesoft Enterprise Peopletools
Version 8.59

Weakness classification

References