GitHub Advisoryadvisory · PyPI

GHSA-5phf-pp7p-vc2r Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection

MEDIUM Published 2021-03-19 Modified 2024-11-18 Official page ↗
Aliases
CVE-2021-28363
Ecosystem
PyPI
Packages
urllib3
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-295
Reviewed
2021-03-19

Affected packages

• PyPI urllib3: >= 1.26.0, < 1.26.4 → fixed in 1.26.4

Description

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. 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 [email protected]

Related

Alias · CVE (1)

  • CVE-2021-28363 The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. vulnerability

Weakness · CWE (1)

  • CWE-295 Improper Certificate Validation weakness

References