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

Update dependency Werkzeug to v2 [SECURITY] #52

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 13, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Werkzeug (changelog) ==0.16.1 -> ==2.2.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.


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 becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency Werkzeug to v2 [SECURITY] Update dependency Werkzeug [SECURITY] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from 2392bdc to 151f04c Compare April 14, 2024 07:28
@renovate renovate bot changed the title Update dependency Werkzeug [SECURITY] Update dependency Werkzeug to v2 [SECURITY] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch 2 times, most recently from 000f006 to 6caf90b Compare April 14, 2024 09:45
@renovate renovate bot changed the title Update dependency Werkzeug to v2 [SECURITY] Update dependency Werkzeug [SECURITY] Apr 14, 2024
@renovate renovate bot changed the title Update dependency Werkzeug [SECURITY] Update dependency Werkzeug to v2 [SECURITY] Apr 14, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from 6caf90b to 8721f82 Compare April 14, 2024 14:18
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from 8721f82 to 4debbad Compare April 22, 2024 11:40
@renovate renovate bot changed the title Update dependency Werkzeug to v2 [SECURITY] Update dependency Werkzeug [SECURITY] Apr 22, 2024
@renovate renovate bot changed the title Update dependency Werkzeug [SECURITY] Update dependency Werkzeug to v2 [SECURITY] Apr 22, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from 4debbad to f070045 Compare April 22, 2024 11:40
@renovate renovate bot changed the title Update dependency Werkzeug to v2 [SECURITY] Update dependency Werkzeug [SECURITY] Apr 27, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from f070045 to f80979d Compare April 27, 2024 09:21
@renovate renovate bot changed the title Update dependency Werkzeug [SECURITY] Update dependency Werkzeug to v2 [SECURITY] Apr 27, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from f80979d to 4045018 Compare April 27, 2024 09:22
@renovate renovate bot changed the title Update dependency Werkzeug to v2 [SECURITY] Update dependency Werkzeug [SECURITY] Apr 28, 2024
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from 4045018 to f9b0031 Compare April 28, 2024 09:50
@renovate renovate bot force-pushed the renovate/pypi-Werkzeug-vulnerability branch from f9b0031 to 6aeacd6 Compare April 28, 2024 13:23
@renovate renovate bot changed the title Update dependency Werkzeug [SECURITY] Update dependency Werkzeug to v2 [SECURITY] Apr 28, 2024
@shaiu shaiu closed this Apr 28, 2024
Copy link
Contributor Author

renovate bot commented Apr 28, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/pypi-Werkzeug-vulnerability branch April 28, 2024 13:30
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.

1 participant