Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 17 vulnerabilities #1

Conversation

philipphomberger
Copy link
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:
    • test-requirements.txt
⚠️ Warning
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.
flake8 5.0.4 has requirement mccabe<0.8.0,>=0.7.0, but you have mccabe 0.6.1.
pytest 6.2.3 has requirement pluggy<1.0.0a1,>=0.12, but you have pluggy 1.2.0.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 624/1000
Why? Has a fix available, CVSS 8.2
Arbitrary Code Execution
SNYK-PYTHON-IPYTHON-2348630
ipython:
5.10.0 -> 8.10.0
No No Known Exploit
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:
5.10.0 -> 8.10.0
No Proof of Concept
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-1086606
pygments:
2.5.2 -> 2.15.0
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PYGMENTS-1088505
pygments:
2.5.2 -> 2.15.0
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-5750273
pygments:
2.5.2 -> 2.15.0
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Exposure of Data Element to Wrong Session
SNYK-PYTHON-REDIS-5291195
redis:
3.5.3 -> 4.3.6
No Proof of Concept
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
medium severity 711/1000
Why? Mature exploit, Has a fix available, CVSS 6.5
Cross-site Scripting (XSS)
SNYK-PYTHON-SPHINX-570772
sphinx:
1.7.9 -> 3.3.0
No Mature
medium severity 701/1000
Why? Mature exploit, Has a fix available, CVSS 6.3
Cross-site Scripting (XSS)
SNYK-PYTHON-SPHINX-570773
sphinx:
1.7.9 -> 3.3.0
No Mature
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SPHINX-5811865
sphinx:
1.7.9 -> 3.3.0
No Proof of Concept
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SPHINX-5812109
sphinx:
1.7.9 -> 3.3.0
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.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
high severity /1000
Why?
Out-of-Bounds Write
SNYK-PYTHON-UJSON-2359034
ujson:
4.0.2 -> 5.4.0
No No Known Exploit
medium severity /1000
Why?
Double Free
SNYK-PYTHON-UJSON-2940619
ujson:
4.0.2 -> 5.4.0
No No Known Exploit
medium severity /1000
Why?
Improper Handling of Syntactically Invalid Structure
SNYK-PYTHON-UJSON-2942122
ujson:
4.0.2 -> 5.4.0
No Proof of Concept

(*) 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)
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 More lessons are available in Snyk Learn

@philipphomberger philipphomberger merged commit e6569e8 into feature/dependencys Dec 8, 2023
1 check was pending
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants