[PR #107] [MERGED] Update dependency requests to v2.31.0 #130
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
TheLovinator/discord-twitter-webhooks#130
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/TheLovinator1/discord-twitter-webhooks/pull/107
Author: @renovate[bot]
Created: 5/22/2023
Status: ✅ Merged
Merged: 5/22/2023
Merged by: @renovate[bot]
Base:
master← Head:renovate/requests-2.x-lockfile📝 Commits (1)
9780b92Update dependency requests to v2.31.0📊 Changes
1 file changed (+3 additions, -3 deletions)
View changed files
📝
poetry.lock(+3 -3)📄 Description
This PR contains the following updates:
2.30.0->2.31.0Release Notes
psf/requests
v2.31.0Compare Source
Security
Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential
forwarding of
Proxy-Authorizationheaders to destination servers whenfollowing HTTPS redirects.
When proxies are defined with user info (https://user:pass@proxy:8080), Requests
will construct a
Proxy-Authorizationheader that is attached to the request toauthenticate with the proxy.
In cases where Requests receives a redirect response, it previously reattached
the
Proxy-Authorizationheader incorrectly, resulting in the value beingsent through the tunneled connection to the destination server. Users who rely on
defining their proxy credentials in the URL are strongly encouraged to upgrade
to Requests 2.31.0+ to prevent unintentional leakage and rotate their proxy
credentials once the change has been fully deployed.
Users who do not use a proxy or do not supply their proxy credentials through
the user information portion of their proxy URL are not subject to this
vulnerability.
Full details can be read in our Github Security Advisory
and CVE-2023-32681.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.