pyradise icon indicating copy to clipboard operation
pyradise copied to clipboard

[Snyk] Fix for 7 vulnerabilities

Open ruefene opened this issue 7 months ago • 0 comments

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:
    • docs/requirements.txt
⚠️ Warning
sphinx-tabs 3.4.4 has requirement docutils~=0.18.0, but you have docutils 0.19.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 531/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 4.2
Remote Code Execution (RCE)
SNYK-PYTHON-IPYTHON-3318382
ipython:
7.34.0 -> 8.10.0
No Proof of Concept
medium severity 444/1000
Why? Has a fix available, CVSS 4.6
Access Control Bypass
SNYK-PYTHON-JUPYTERSERVER-5862881
jupyter-server:
1.24.0 -> 2.7.2
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Open Redirect
SNYK-PYTHON-JUPYTERSERVER-5862882
jupyter-server:
1.24.0 -> 2.7.2
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:
39.0.1 -> 65.5.1
No No Known Exploit
low severity 384/1000
Why? Has a fix available, CVSS 3.4
Open Redirect
SNYK-PYTHON-TORNADO-5537286
tornado:
6.2 -> 6.3.3
No No Known Exploit
medium severity 494/1000
Why? Has a fix available, CVSS 5.6
HTTP Request Smuggling
SNYK-PYTHON-TORNADO-5840803
tornado:
6.2 -> 6.3.3
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
HTTP Request Smuggling
SNYK-PYTHON-TORNADO-6041512
tornado:
6.2 -> 6.3.3
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:

🦉 Remote Code Execution (RCE) 🦉 Access Control Bypass 🦉 Open Redirect 🦉 More lessons are available in Snyk Learn

ruefene avatar Nov 23 '23 15:11 ruefene