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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 5 vulnerabilities #1232

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

Conversation

0xGodson
Copy link
Owner

@0xGodson 0xGodson commented Mar 5, 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:
    • CMD4/requirements.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Insufficient Verification of Data Authenticity
SNYK-PYTHON-CERTIFI-3164749
certifi:
2021.10.8 -> 2023.7.22
No No Known Exploit
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:
2021.10.8 -> 2023.7.22
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 344/1000
Why? Has a fix available, CVSS 2.6
Access Restriction Bypass
SNYK-PYTHON-WERKZEUG-3319935
werkzeug:
1.0.1 -> 2.2.3
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.2.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:

馃 Cross-site Scripting (XSS)
馃 Access Restriction Bypass
馃 Denial of Service (DoS)

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