[Snyk] Security upgrade tornado from 6.2 to 6.3.2

[AdamOswald]

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

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

visualdl 2.5.2 has requirement gradio==3.11.0, but you have gradio 3.30.0.
visualdl 2.5.2 has requirement paddle2onnx>=1.0.5, but you have paddle2onnx 0.9.5.
torch 1.13.1 requires nvidia-cuda-nvrtc-cu11, which is not installed.
torch 1.13.1 requires nvidia-cudnn-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-runtime-cu11, which is not installed.
torch 1.13.1 requires nvidia-cublas-cu11, which is not installed.
tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1.
streamlit 1.22.0 requires tornado, which is not installed.
streamlit 1.22.0 has requirement altair<5,>=3.2.0, but you have altair 5.0.0.
scikit-learn 1.0.2 requires scipy, which is not installed.
powerlaw 1.5 requires scipy, which is not installed.
pipenv 2023.4.29 has requirement setuptools>=67.0.0, but you have setuptools 39.0.1.
paddlepaddle 2.4.2 has requirement protobuf<=3.20.0,>=3.1.0, but you have protobuf 3.20.3.
paddlenlp 2.5.2 has requirement dill<0.3.5, but you have dill 0.3.6.
paddlenlp 2.5.2 has requirement multiprocess<=0.70.12.2, but you have multiprocess 0.70.14.
paddle2onnx 0.9.5 has requirement onnx<=1.9.0, but you have onnx 1.14.0.
openvino 2021.4.2 has requirement numpy<1.20,>=1.16.6, but you have numpy 1.21.3.
onnxruntime 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3.
onnxruntime-gpu 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3.
lpips 0.1.4 requires scipy, which is not installed.
google-auth 2.18.0 has requirement urllib3<2.0, but you have urllib3 2.0.2.
filterpy 1.4.5 requires scipy, which is not installed.
facexlib 0.3.0 requires scipy, which is not installed.
botocore 1.29.135 has requirement urllib3<1.27,>=1.25.4, but you have urllib3 2.0.2.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	556/1000 Why? Recently disclosed, Has a fix available, CVSS 5.4	Open Redirect SNYK-PYTHON-TORNADO-5537286	tornado: 6.2 -> 6.3.2	No	No Known Exploit

(*) 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:

🦉 Open Redirect

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[secure-code-warrior-for-github]

Micro-Learning Topic: Open redirect (Detected by phrase)

Matched on "Open Redirect"

What is this? (2min video)

This vulnerability refers to the ability of an attacker to arbitrarily perform a redirection (external) or forward (internal) against the system. It arises due to insufficient validation or sanitisation of inputs used to perform a redirect or forward and may result in privilege escalation (in the case of a forward) or may be used to launch phishing attacks against users (in the case of redirects).

Try a challenge in Secure Code Warrior

Helpful references

• OWASP Unvalidated Redirects and Forwards Cheat Sheet - This cheatsheet is focused on providing clear, simple, actionable guidance for preventing redirection and forwarding flaws in your applications.
• Preventing Open Redirection Attacks (C#) - A detailed Microsoft article on how to prevent open redirection vulnerabilities in ASP.NET MVC.

[senior-dev-bot]

Hi there! 👋 Thanks for opening a PR. 🎉
To get the most out of Senior Dev, please uninstall the app from your organization, then re-install it into your organization. You can uninstall the app here 🚀

[difflens]

View changes in DiffLens

[viezly]

Changes preview:

Legend:

👀 Review pull request on Viezly

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 1

Change summary by file extension:
.txt : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.