[Snyk] Security upgrade werkzeug from 2.2.3 to 3.0.3 #284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6808933
perdelt
added a commit
that referenced
this pull request
Jul 12, 2024
* TPC-H: Show RAM cached in summary * Bexhoma: monitor_cluster_exists * TPC-H: More details about monitoring in summary * DBMSBenchmarker: Current dev version v0.13.7 * TPC-H: More details about monitoring in summary * Bexhoma: test_if_monitoring_healthy() * Bexhoma: test_if_monitoring_healthy() with cURL * Bexhoma: Monitoring docs * Bexhoma: Also mount bexhoma-data in dashboard * Bexhoma: Show content of result folder as CLI tool * Docs: Config * Bexhoma: Improved output and docs * PostgreSQL: More time for shutdown * Bexhoma: Restarting SUT waits for its removal first * PostgreSQL: lifecycle user rights issue * Bexhoma: Label PV with usage information * PostgreSQL: lifecycle tests with gosu * Bexhoma: Show volume infos in status * Bexhoma: Ceil() loading times * YCSB: Show connection infos in summary * Bexhoma: Show code in results table * YCSB: Show connection infos * Bexhoma: show_summary_monitoring() * Bexhoma: Test for unified monitoring summary * Bexhoma: config.check_volumes() * TPC-H: Too many pods test for generator * Bexhoma: Show infos about workload in summary * Bexhoma: Also mount bexhoma-data in dashboard * Bexhoma: show localresults * Bexhoma: Do not start daemonset if monitoring in cluster exists * Bexhoma: show data dir content in tool * Bexhoma: Loader metrics also for cluster monitoring exists * Bexhoma: Improved output and docs * TPC-H: MariaDB * Example custom SQL workload * Bexhoma: List of DBMS per experiment * YCSB: Implement YugaByteDB again * Bexhoma: Allow placeholder namespace in JDBC connection string and in script commands * fix: requirements.txt to reduce vulnerabilities (#279) * fix: requirements.txt to reduce vulnerabilities (#281) * Bexhoma: Default summary for DBMSBenchmarker follows TPC-H * Experiment: Prepare TPCx-AI * fix: requirements.txt to reduce vulnerabilities (#284) * fix: images/benchmarker_dbmsbenchmarker/requirements.txt to reduce vulnerabilities (#288) * fix: requirements.txt to reduce vulnerabilities (#287) * Action: Publish only on release * Benchmarker: Catch error if volume is missing * README: Link corrected * fix: requirements.txt to reduce vulnerabilities (#293) * fix: images/benchmarker_dbmsbenchmarker/requirements.txt to reduce vulnerabilities (#292) * Docs: Typos and remove old texts * Test: No urllib3 * Images: we only need packages required by dbmsbenchmarker for benchmarker container * Docs: Include monitoring * TPC-H: More helpful infos per workload in results * Test: We need urllib3, because of security warnings * Docs: Improved output * Bexhoma: Bugfix cluster monitoring exists * Bexhoma: Bugfix cluster monitoring * Bexhoma: Bugfix missing dashboard * MySQL: Default to mysql:8.4.0 * MariaDB: Current version * MariaDB: Removed some MySQL settings * Docs: Improved output * DBMSBenchmarker: Dev channel * DBMSBenchmarker: Dockerfiles v0.13.7 and dev * DBMSBenchmarker: dev option in YAML * DBMSBenchmarker: :v0.14.0 * Docs: Improved output * MonetDB: New JDBC driver * Benchbase: Prepare unified evaluation * Clustermanager: Show use case per experiment * HammerDB: Prepare unified evaluation * YugabyteDB: Prepare demo * YugabyteDB: Prepare demo in YCSB * HammerDB: Prepare unified evaluation * Benchbase: Prepare unified evaluation * YugabyteDB: Prepare demo in YCSB * HammerDB: Prepare unified evaluation * fix: requirements.txt to reduce vulnerabilities (#299) * Benchbase: Prepare unified evaluation * Updated output of several use cases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 7.5
SNYK-PYTHON-WERKZEUG-6808933
werkzeug:2.2.3 -> 3.0.3(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Remote Code Execution (RCE)