You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: HISTORY.md
+27
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,33 @@ dev
6
6
7
7
-\[Short description of non-trivial change.\]
8
8
9
+
2.31.0 (2023-05-22)
10
+
-------------------
11
+
12
+
**Security**
13
+
- Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential
14
+
forwarding of `Proxy-Authorization` headers to destination servers when
15
+
following HTTPS redirects.
16
+
17
+
When proxies are defined with user info (https://user:pass@proxy:8080), Requests
18
+
will construct a `Proxy-Authorization` header that is attached to the request to
19
+
authenticate with the proxy.
20
+
21
+
In cases where Requests receives a redirect response, it previously reattached
22
+
the `Proxy-Authorization` header incorrectly, resulting in the value being
23
+
sent through the tunneled connection to the destination server. Users who rely on
24
+
defining their proxy credentials in the URL are *strongly* encouraged to upgrade
25
+
to Requests 2.31.0+ to prevent unintentional leakage and rotate their proxy
26
+
credentials once the change has been fully deployed.
27
+
28
+
Users who do not use a proxy or do not supply their proxy credentials through
29
+
the user information portion of their proxy URL are not subject to this
30
+
vulnerability.
31
+
32
+
Full details can be read in our [Github Security Advisory](https://github.com/psf/requests/security/advisories/GHSA-j8r2-6x86-q33q)
33
+
and [CVE-2023-32681](https://nvd.nist.gov/vuln/detail/CVE-2023-32681).
0 commit comments