[Snyk] Security upgrade werkzeug from 2.2.3 to 3.0.6

[pavelbe4solutions]

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• dev_requirements.txt

⚠️ Warning

tensorboard 2.11.2 requires werkzeug, which is not installed.
scikit-learn 1.0.2 requires scipy, which is not installed.
multiprocess 0.70.15 has requirement dill>=0.3.7, but you have dill 0.3.6.
flake8 5.0.4 has requirement importlib-metadata<4.3,>=1.1.0; python_version < "3.8", but you have importlib-metadata 6.7.0.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal
🦉 Allocation of Resources Without Limits or Throttling

[dryrunsecurity]

DryRun Security Summary

This pull request updates the dependencies in the dev_requirements.txt file, most notably adding the werkzeug>=3.0.6 dependency to address a vulnerability in a previous version of the Werkzeug library.

Expand for full summary

Summary:

The changes made in this pull request are focused on updating the dependencies listed in the dev_requirements.txt file. The most notable change is the addition of the werkzeug>=3.0.6 dependency, which is being pinned by a tool called "Snyk" to avoid a vulnerability in a previous version of the Werkzeug library.

Addressing vulnerabilities in third-party dependencies is a critical aspect of maintaining the security of an application. Vulnerabilities in these dependencies can potentially be exploited by attackers to gain unauthorized access, execute malicious code, or perform other malicious actions. By proactively updating the Werkzeug dependency to a version that is not affected by the identified vulnerability, the development team is taking steps to mitigate these risks and improve the overall security of the application.

It's a good practice to regularly review the dependencies used in a project and ensure that they are up-to-date and free of known vulnerabilities. This can be done through the use of tools like Snyk, which can help identify and track vulnerabilities in dependencies, as well as by manually reviewing the changes made to the dev_requirements.txt file.

Files Changed:

• dev_requirements.txt: This file contains the list of dependencies for the development environment. The changes include adding a new dependency, werkzeug>=3.0.6, which is being pinned by the Snyk tool to avoid a vulnerability in a previous version of the Werkzeug library.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.