urllib3: HTTPS proxy TLS configuration may be ignored or overridden
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| urllib3 | urllib3 | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Urllib3 | Urllib3 |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8988-9cw3-xx77 | urllib3: HTTPS proxy TLS configuration may be ignored or overridden |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.206% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Python
Python urllib3 |
|
| CPEs | cpe:2.3:a:python:urllib3:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Python
Python urllib3 |
|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Urllib3
Urllib3 urllib3 |
|
| Vendors & Products |
Urllib3
Urllib3 urllib3 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0. | |
| Title | urllib3: HTTPS proxy TLS configuration may be ignored or overridden | |
| Weaknesses | CWE-295 CWE-440 |
|
| References |
|
|
| Metrics |
cvssV4_0
|