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

fix(deps): update dependency werkzeug to v3 [security] #253

Merged
merged 2 commits into from
Jun 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2023

Mend Renovate

This PR contains the following updates:

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

Review

  • Updates have been tested and work
  • If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

GitHub Vulnerability Alerts

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 - "" in timezone America/Montreal, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 86fd0e8 to 19d025a Compare November 1, 2023 19:34
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 3 times, most recently from 328fd78 to 211d225 Compare November 8, 2023 21:11
@renovate renovate bot changed the title fix(deps): update dependency werkzeug to v3 [security] fix(deps): 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 22:36
@renovate renovate bot changed the title fix(deps): update dependency werkzeug to v3 [security] - autoclosed fix(deps): 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 03:42
@renovate renovate bot changed the title fix(deps): update dependency werkzeug to v3 [security] fix(deps): update dependency werkzeug to v2.3.8 [security] Nov 14, 2023
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 3 times, most recently from 874aef5 to 8762c4a Compare November 20, 2023 20:59
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 4 times, most recently from f8fd773 to 1aaeb40 Compare November 29, 2023 17:04
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 1aaeb40 to 539f05d Compare December 20, 2023 17:41
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 539f05d to 54dbef5 Compare January 3, 2024 19:51
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 4 times, most recently from b5835f9 to fc7d6c8 Compare January 16, 2024 18:39
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 4 times, most recently from fd9c6f2 to 6b5b265 Compare February 1, 2024 19:22
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 3 times, most recently from 196d532 to 31c8d18 Compare March 11, 2024 14:53
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 31c8d18 to 583177f Compare March 28, 2024 19:02
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 583177f to 4038058 Compare April 15, 2024 11:56
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 7 times, most recently from 6259d07 to 960bc8e Compare April 29, 2024 15:19
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 960bc8e to e314900 Compare May 1, 2024 18:24
@renovate renovate bot changed the title fix(deps): update dependency werkzeug to v2.3.8 [security] fix(deps): update dependency werkzeug to v3 [security] May 6, 2024
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 2 times, most recently from 4e964eb to e7c7196 Compare May 9, 2024 19:31
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 2 times, most recently from b71e17d to 26134df Compare May 21, 2024 17:31
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch 3 times, most recently from edb3aae to 7b414b5 Compare June 4, 2024 17:26
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 7b414b5 to 0fcb117 Compare June 5, 2024 15:37
@renovate renovate bot force-pushed the renovate/pypi-werkzeug-vulnerability branch from 0fcb117 to 91b720e Compare June 11, 2024 21:37
Copy link
Contributor Author

renovate bot commented Jun 18, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Copy link
Contributor

@whabanks whabanks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested the changes locally by hooking utils up to both admin and api and running the apps / testing functionality.

@whabanks whabanks merged commit d67d776 into main Jun 18, 2024
4 checks passed
@whabanks whabanks deleted the renovate/pypi-werkzeug-vulnerability branch June 18, 2024 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant