Sourced fromrequests's releases.

v2.31.0

2.31.0 (2023-05-22)

Security

• Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potentialforwarding ofProxy-Authorization headers to destination servers whenfollowing HTTPS redirects.

  When proxies are defined with user info (https://user:pass@proxy:8080), Requestswill construct aProxy-Authorization header that is attached to the request toauthenticate with the proxy.

  In cases where Requests receives a redirect response, it previously reattachedtheProxy-Authorization header incorrectly, resulting in the value beingsent through the tunneled connection to the destination server. Users who rely ondefining their proxy credentials in the URL arestrongly encouraged to upgradeto Requests 2.31.0+ to prevent unintentional leakage and rotate their proxycredentials once the change has been fully deployed.

  Users who do not use a proxy or do not supply their proxy credentials throughthe user information portion of their proxy URL are not subject to thisvulnerability.

  Full details can be read in ourGithub Security AdvisoryandCVE-2023-32681.

Sourced fromrequests's changelog.

2.31.0 (2023-05-22)

Security

• Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potentialforwarding ofProxy-Authorization headers to destination servers whenfollowing HTTPS redirects.

  When proxies are defined with user info (https://user:pass@proxy:8080), Requestswill construct aProxy-Authorization header that is attached to the request toauthenticate with the proxy.

  In cases where Requests receives a redirect response, it previously reattachedtheProxy-Authorization header incorrectly, resulting in the value beingsent through the tunneled connection to the destination server. Users who rely ondefining their proxy credentials in the URL arestrongly encouraged to upgradeto Requests 2.31.0+ to prevent unintentional leakage and rotate their proxycredentials once the change has been fully deployed.

  Users who do not use a proxy or do not supply their proxy credentials throughthe user information portion of their proxy URL are not subject to thisvulnerability.

  Full details can be read in ourGithub Security AdvisoryandCVE-2023-32681.

• 147c851 v2.31.0
• 74ea7cf Merge pull request fromGHSA-j8r2-6x86-q33q
• 3022253 test on pypy 3.8 and pypy 3.9 on windows and macos (#6424)
• b639e66 test on py3.12 (#6448)
• d3d5044 Fixed a small typo (#6452)
• See full diff incompare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from theSecurity Alerts page.