urllib3@1.15 vulnerabilities
HTTP library with thread-safe connection pooling, file post, and more.
-
latest version
2.2.3
-
latest non vulnerable version
-
first published
15 years ago
-
latest version published
2 months ago
-
licenses detected
- [0,)
Direct Vulnerabilities
Known vulnerabilities in the urllib3 package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Improper Removal of Sensitive Information Before Storage or Transfer due to the improper handling of the Notes: To be vulnerable, the application must be doing all of the following:
How to fix Improper Removal of Sensitive Information Before Storage or Transfer? Upgrade |
[,1.26.19)
[2.0.0a1,2.2.2)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Information Exposure Through Sent Data when it processes HTTP redirects with a 303 status code, due to not stripping the request body when changing the request method from Note: This is only exploitable if sensitive information is being submitted in the HTTP request body and the origin service is compromised, starting to redirect using 303 to a malicious peer or the redirected-to service becomes compromised. How to fix Information Exposure Through Sent Data? Upgrade |
[,1.26.18)
[2.0.0,2.0.7)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Information Exposure Through Sent Data when the Notes: This is only exploitable if a redirect differs in host, port, or scheme. Due to the How to fix Information Exposure Through Sent Data? Upgrade |
[,1.24.2)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Information Exposure Through Sent Data when the Note: This is only exploitable if the user is using the ##Workaround: This vulnerability can be mitigated by disabling HTTP redirects using How to fix Information Exposure Through Sent Data? Upgrade |
[,1.26.17)
[2.0.0,2.0.6)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the If a URL is passed as a parameter or redirected to via an HTTP redirect and it contains many How to fix Regular Expression Denial of Service (ReDoS)? Upgrade |
[,1.26.5)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to HTTP Header Injection. The 'method' parameter is not filtered to prevent the injection from altering the entire request. For example:
This will result in the following request being generated:
How to fix HTTP Header Injection? Upgrade |
[,1.25.9)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Improper Certificate Validation. It mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates. This can result in SSL connections succeeding in situations where it should have failed. How to fix Improper Certificate Validation? Upgrade |
[,1.24.2)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to CRLF injection. Attacker who has the control of the requesting address parameter, could manipulate an HTTP header and attack an internal service. How to fix CRLF injection? Upgrade |
[,1.24.3)
|
urllib3 is a HTTP library with thread-safe connection pooling, file post, and more. Affected versions of this package are vulnerable to Authentication Bypass. It did remove the Authorization HTTP header when following a cross-origin redirect. This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext. How to fix Authentication Bypass? Upgrade urllib3 to version 1.23 or higher. |
[,1.23)
|