Description
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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0457 | 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. |
Github GHSA |
GHSA-5phf-pp7p-vc2r | Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-03T21:40:14.323Z
Reserved: 2021-03-13T00:00:00.000Z
Link: CVE-2021-28363
No data.
Status : Modified
Published: 2021-03-15T18:15:19.017
Modified: 2024-11-21T05:59:35.823
Link: CVE-2021-28363
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA