Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update dependency werkzeug to v3 [SECURITY] #99

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
werkzeug (changelog) ==2.2.2 -> ==3.0.3 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-23934

Browsers may allow "nameless" cookies that look like =value instead of key=value. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like =__Host-test=bad for another subdomain.

Werkzeug <= 2.2.2 will parse the cookie =__Host-test=bad as __Host-test=bad. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key.

CVE-2023-25577

Werkzeug's multipart form data parser will parse an unlimited number of parts, including file parts. Parts can be a small amount of bytes, but each requires CPU time to parse and may use more memory as Python data. If a request can be made to an endpoint that accesses request.data, request.form, request.files, or request.get_data(parse_form_data=False), it can cause unexpectedly high resource usage.

This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. The amount of RAM required can trigger an out of memory kill of the process. Unlimited file parts can use up memory and file handles. If many concurrent requests are sent continuously, this can exhaust or kill all available workers.

CVE-2023-46136

Werkzeug multipart data parser needs to find a boundary that may be between consecutive chunks. That's why parsing is based on looking for newline characters. Unfortunately, code looking for partial boundary in the buffer is written inefficiently, so if we upload a file that starts with CR or LF and then is followed by megabytes of data without these characters: all of these bytes are appended chunk by chunk into internal bytearray and lookup for boundary is performed on growing buffer.

This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. The amount of RAM required can trigger an out of memory kill of the process. If many concurrent requests are sent continuously, this can exhaust or kill all available workers.

CVE-2024-34069

The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger.


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner October 25, 2023 18:59
@renovate renovate bot changed the title chore: Update dependency werkzeug to v3 [SECURITY] chore: Update dependency werkzeug to v3 [SECURITY] - autoclosed Nov 13, 2023
@renovate renovate bot closed this Nov 13, 2023
@renovate renovate bot deleted the renovate/pypi-werkzeug-vulnerability branch November 13, 2023 23:13
@renovate renovate bot changed the title chore: Update dependency werkzeug to v3 [SECURITY] - autoclosed chore: Update dependency werkzeug to v3 [SECURITY] Nov 14, 2023
@renovate renovate bot reopened this Nov 14, 2023
@renovate renovate bot restored the renovate/pypi-werkzeug-vulnerability branch November 14, 2023 02:07
@renovate renovate bot changed the title chore: Update dependency werkzeug to v3 [SECURITY] chore: Update dependency werkzeug to v2.3.8 [SECURITY] Nov 14, 2023
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from ce08067 to a6cb240 Compare November 14, 2023 02:07
@renovate renovate bot changed the title chore: Update dependency werkzeug to v2.3.8 [SECURITY] chore: Update dependency werkzeug to v2.3.8 [SECURITY] - autoclosed Apr 3, 2024
@renovate renovate bot closed this Apr 3, 2024
@renovate renovate bot deleted the renovate/pypi-werkzeug-vulnerability branch April 3, 2024 13:17
@renovate renovate bot changed the title chore: Update dependency werkzeug to v2.3.8 [SECURITY] - autoclosed chore: Update dependency werkzeug to v2.3.8 [SECURITY] Apr 3, 2024
@renovate renovate bot restored the renovate/pypi-werkzeug-vulnerability branch April 3, 2024 16:30
@renovate renovate bot reopened this Apr 3, 2024
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from a6cb240 to fdf3340 Compare April 3, 2024 16:30
@renovate renovate bot changed the title chore: Update dependency werkzeug to v2.3.8 [SECURITY] chore: Update dependency werkzeug to v3 [SECURITY] Aug 6, 2024
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 2 times, most recently from 03104c1 to 07aeb0c Compare August 6, 2024 16:13
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 07aeb0c to 437cc35 Compare August 7, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants