Skip to content
This repository was archived by the owner on Nov 6, 2024. It is now read-only.

[Snyk] Security upgrade werkzeug from 2.2.2 to 3.0.6#199

Open
entroychang wants to merge 1 commit intomainfrom
snyk-fix-aba41dfe199bec5933c24d756b47ec54
Open

[Snyk] Security upgrade werkzeug from 2.2.2 to 3.0.6#199
entroychang wants to merge 1 commit intomainfrom
snyk-fix-aba41dfe199bec5933c24d756b47ec54

Conversation

@entroychang
Copy link
Copy Markdown
Collaborator

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt
⚠️ Warning
virtualenv 20.26.6 has requirement distlib<1,>=0.3.7, but you have distlib 0.3.6.
virtualenv 20.26.6 has requirement filelock<4,>=3.12.2, but you have filelock 3.8.0.
virtualenv 20.26.6 has requirement platformdirs<5,>=3.9.1, but you have platformdirs 2.5.2.
Flask 2.2.2 requires Werkzeug, which is not installed.

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants