[Security] Bump urllib3 from 2.0.4 to 2.0.7
Bumps urllib3 from 2.0.4 to 2.0.7. This update includes security fixes.
Vulnerabilities fixed
Cookie
HTTP header isn't stripped on cross-origin redirects urllib3 doesn't treat theCookie
HTTP header special or provide any helpers for managing cookies over HTTP, that is the responsibility of the user. However, it is possible for a user to specify aCookie
header and unknowingly leak information via HTTP redirects to a different origin if that user doesn't disable redirects explicitly.Users must handle redirects themselves instead of relying on urllib3's automatic redirects to achieve safe processing of the
Cookie
header, thus we decided to strip the header by default in order to further protect users who aren't using the correct approach.Affected usages
We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited:
- Using an affected version of urllib3 (patched in v1.26.17 and v2.0.6)
- Using the
Cookie
header on requests, which is mostly typical for impersonating a browser.- Not disabling HTTP redirects
- Either not using HTTPS or for the origin server to redirect to a malicious origin.
Remediation
- Upgrading to at least urllib3 v1.26.17 or v2.0.6
- Disabling HTTP redirects using
redirects=False
when sending requests.- Not using the
Cookie
header.Patched versions: 2.0.6 Affected versions: >= 2.0.0, < 2.0.6
urllib3's request body not stripped after redirect from 303 status changes request method to GET urllib3 previously wouldn't remove the HTTP request body when an HTTP redirect response using status 303 "See Other" after the request had its method changed from one that could accept a request body (like
POST
) toGET
as is required by HTTP RFCs. Although the behavior of removing the request body is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers.From RFC 9110 Section 9.3.1:
A client SHOULD NOT generate content in a GET request unless it is made directly to an origin server that has previously indicated, in or out of band, that such a request has a purpose and will be adequately supported.
Affected usages
Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren't putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn't exploitable.
Both of the following conditions must be true to be affected by this vulnerability:
- If you're using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON)
- The origin service is compromised and starts redirecting using 303 to a malicious peer or the redirected-to service becomes compromised.
Remediation
You can remediate this vulnerability with any of the following steps:
- Upgrade to a patched version of urllib3 (v1.26.18 or v2.0.7)
... (truncated)
Patched versions: 2.0.7 Affected versions: >= 2.0.0, <= 2.0.6
Release notes
Sourced from urllib3's releases.
2.0.7
- Made body stripped from HTTP requests changing the request method to GET after HTTP 303 "See Other" redirect responses. (GHSA-g4mx-q9vg-27p4)
2.0.6
- Added the
Cookie
header to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set viaRetry.remove_headers_on_redirect
. (GHSA-v845-jxx5-vc9f)2.0.5
Changelog
Sourced from urllib3's changelog.
2.0.7 (2023-10-17)
- Made body stripped from HTTP requests changing the request method to GET after HTTP 303 "See Other" redirect responses.
2.0.6 (2023-10-02)
- Added the
Cookie
header to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set viaRetry.remove_headers_on_redirect
.2.0.5 (2023-09-20)
- Allowed pyOpenSSL third-party module without any deprecation warning. (
[#3126](https://github.com/urllib3/urllib3/issues/3126) <https://github.com/urllib3/urllib3/issues/3126>
__)- Fixed default
blocksize
ofHTTPConnection
classes to match high-level classes. Previously was 8KiB, now 16KiB. ([#3066](https://github.com/urllib3/urllib3/issues/3066) <https://github.com/urllib3/urllib3/issues/3066>
__)
Commits
-
56f01e0
Release 2.0.7 -
4e50fbc
Merge pull request from GHSA-g4mx-q9vg-27p4 -
80808b0
Fix docs build on Python 3.12 (#3144) -
f28deff
Add 1.26.17 to the current changelog -
262e3e3
Release 2.0.6 -
644124e
Merge pull request from GHSA-v845-jxx5-vc9f -
740380c
Bump cryptography from 41.0.3 to 41.0.4 (#3131) -
d9f85a7
Release 2.0.5 -
d41f412
Undeprecate pyOpenSSL module (#3127) -
b6c04cb
Fix a link to "absolute URI" definition (#3128) - Additional commits viewable in compare view