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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Fix for 14 vulnerabilities #938

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Fix for 14 vulnerabilities #938

wants to merge 1 commit into from

Conversation

ccs-snyk
Copy link

@ccs-snyk ccs-snyk commented Mar 7, 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-dev.txt
⚠️ Warning 
moto 2.0.9 requires werkzeug, which is not installed.
Jinja2 3.1.3 has requirement MarkupSafe>=2.0, but you have MarkupSafe 1.1.1.
Flask 2.2.5 requires Werkzeug, which is not installed.
Flask 2.2.5 has requirement itsdangerous>=2.0, but you have itsdangerous 1.1.0.
Flask 2.2.5 has requirement click>=8.0, but you have click 7.1.2.
Flask-Login 0.6.2 requires Werkzeug, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
critical severity 704/1000
Why? Has a fix available, CVSS 9.8		 Improper Following of a Certificate's Chain of Trust
SNYK-PYTHON-CERTIFI-5805047		 certifi:
2022.12.7 -> 2023.7.22
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9		 Use of a Broken or Risky Cryptographic Algorithm
SNYK-PYTHON-CRYPTOGRAPHY-6149518		 cryptography:
39.0.2 -> 42.0.4
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9		 Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-PYTHON-CRYPTOGRAPHY-6157248		 cryptography:
39.0.2 -> 42.0.4
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9		 NULL Pointer Dereference
SNYK-PYTHON-CRYPTOGRAPHY-6261585		 cryptography:
39.0.2 -> 42.0.4
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5		 Information Exposure
SNYK-PYTHON-FLASK-5490129		 flask:
1.1.4 -> 2.2.5
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.11.3 -> 3.1.3
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:
4.5.1 -> 4.5.4
No Proof of Concept
medium severity 429/1000
Why? Has a fix available, CVSS 4.3		 Exposure of Data Element to Wrong Session
SNYK-PYTHON-REDIS-5291196		 redis:
4.5.1 -> 4.5.4
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1		 Information Exposure
SNYK-PYTHON-REQUESTS-5595532		 requests:
2.28.2 -> 2.31.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9		 Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-5926907		 urllib3:
1.26.5 -> 1.26.18
No No Known Exploit
medium severity 424/1000
Why? Has a fix available, CVSS 4.2		 Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-6002459		 urllib3:
1.26.5 -> 1.26.18
No No Known Exploit
low severity 344/1000
Why? Has a fix available, CVSS 2.6		 Access Restriction Bypass
SNYK-PYTHON-WERKZEUG-3319935		 werkzeug:
1.0.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:
1.0.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:
1.0.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:

🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')
🦉 NULL Pointer Dereference
🦉 More lessons are available in Snyk Learn

@snyk-bot
fix: requirements-dev.txt to reduce vulnerabilities
991cd39 
The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-CERTIFI-5805047
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6149518
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6157248
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6261585
- https://snyk.io/vuln/SNYK-PYTHON-FLASK-5490129
- https://snyk.io/vuln/SNYK-PYTHON-JINJA2-6150717
- https://snyk.io/vuln/SNYK-PYTHON-REDIS-5291195
- https://snyk.io/vuln/SNYK-PYTHON-REDIS-5291196
- https://snyk.io/vuln/SNYK-PYTHON-REQUESTS-5595532
- https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-5926907
- https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-6002459
- https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-3319935
- https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-3319936
- https://snyk.io/vuln/SNYK-PYTHON-WERKZEUG-6035177
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ccs-snyk @snyk-bot