Skip to content

[Snyk] Fix for 5 vulnerabilities#21

Open
ulf1 wants to merge 1 commit into
mainfrom
snyk-fix-5c461a5e3e1e56b0ab0c647ad5b2466f
Open

[Snyk] Fix for 5 vulnerabilities#21
ulf1 wants to merge 1 commit into
mainfrom
snyk-fix-5c461a5e3e1e56b0ab0c647ad5b2466f

Conversation

@ulf1

@ulf1 ulf1 commented Aug 8, 2023

Copy link
Copy Markdown
Owner

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-demo.txt
⚠️ Warning
Quandl 3.7.0 requires numpy, which is not installed.
pandas 1.3.5 requires numpy, which is not installed.
matplotlib 3.5.3 requires numpy, which is not installed.
jupyter-server-ydoc 0.6.2 has requirement ypy-websocket<0.9.0,>=0.8.2, but you have ypy-websocket 0.12.1.

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
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
NULL Pointer Dereference
SNYK-PYTHON-NUMPY-2321964
numpy:
1.21.3 -> 1.22.2
No Proof of Concept
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Buffer Overflow
SNYK-PYTHON-NUMPY-2321966
numpy:
1.21.3 -> 1.22.2
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Denial of Service (DoS)
SNYK-PYTHON-NUMPY-2321970
numpy:
1.21.3 -> 1.22.2
No Proof of Concept
low severity 384/1000
Why? Has a fix available, CVSS 3.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:

🦉 Remote Code Execution (RCE)
🦉 NULL Pointer Dereference
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants