Skip to content

Conversation

@CharaD7
Copy link
Owner

@CharaD7 CharaD7 commented Feb 18, 2024

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
Jinja2 3.1.3 requires MarkupSafe, which is not installed.
Flask 2.2.5 requires Werkzeug, which is not installed.
Flask 2.2.5 has requirement click>=8.0, but you have click 6.7.
Flask 2.2.5 has requirement itsdangerous>=2.0, but you have itsdangerous 0.24.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Improper Input Validation
SNYK-PYTHON-FLASK-42185
flask:
0.12 -> 2.2.5
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-FLASK-451637
flask:
0.12 -> 2.2.5
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Information Exposure
SNYK-PYTHON-FLASK-5490129
flask:
0.12 -> 2.2.5
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-JINJA2-1012994
jinja2:
2.9.5 -> 3.1.3
No Proof of Concept
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Sandbox Escape
SNYK-PYTHON-JINJA2-174126
jinja2:
2.9.5 -> 3.1.3
No No Known Exploit
medium severity 484/1000
Why? Has a fix available, CVSS 5.4
Cross-site Scripting (XSS)
SNYK-PYTHON-JINJA2-6150717
jinja2:
2.9.5 -> 3.1.3
No No Known Exploit
high severity 604/1000
Why? Has a fix available, CVSS 7.8
Improper Privilege Management
SNYK-PYTHON-JUPYTERCORE-3063766
jupyter-core:
4.3.0 -> 4.11.2
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.13.0 -> 2.31.0
No No Known Exploit
critical severity 811/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
Information Exposure
SNYK-PYTHON-REQUESTS-72435
requests:
2.13.0 -> 2.31.0
No Proof of Concept
high severity 761/1000
Why? Mature exploit, Has a fix available, CVSS 7.5
Directory Traversal
SNYK-PYTHON-WERKZEUG-3266409
werkzeug:
0.12.1 -> 2.3.8
No Mature
low severity 344/1000
Why? Has a fix available, CVSS 2.6
Access Restriction Bypass
SNYK-PYTHON-WERKZEUG-3319935
werkzeug:
0.12.1 -> 2.3.8
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-WERKZEUG-3319936
werkzeug:
0.12.1 -> 2.3.8
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Insufficient Randomness
SNYK-PYTHON-WERKZEUG-458931
werkzeug:
0.12.1 -> 2.3.8
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Inefficient Algorithmic Complexity
SNYK-PYTHON-WERKZEUG-6035177
werkzeug:
0.12.1 -> 2.3.8
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:

🦉 Improper Input Validation
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 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.

3 participants