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 11 vulnerabilities #18

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

Conversation

Dixiejane
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:
    • deps/uv/docs/requirements.txt
⚠️ Warning
Jinja2 3.1.3 has requirement MarkupSafe>=2.0, but you have MarkupSafe 1.1.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 439/1000
Why? Has a fix available, CVSS 4.5
Directory Traversal
SNYK-PYTHON-BABEL-1278589
babel:
2.9.0 -> 2.9.1
No No Known Exploit
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Insufficient Verification of Data Authenticity
SNYK-PYTHON-CERTIFI-3164749
certifi:
2019.11.28 -> 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:
2019.11.28 -> 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
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-5750273
pygments:
2.8.1 -> 2.15.0
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.22.0 -> 2.31.0
No No Known Exploit
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
high severity 599/1000
Why? Has a fix available, CVSS 7.7
HTTP Header Injection
SNYK-PYTHON-URLLIB3-1014645
urllib3:
1.25.8 -> 1.26.18
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.25.8 -> 1.26.18
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.25.8 -> 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.25.8 -> 1.26.18
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:

🦉 Directory Traversal
🦉 Cross-site Scripting (XSS)
🦉 Regular Expression Denial of Service (ReDoS)

Copy link

vercel bot commented Feb 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
node ❌ Failed (Inspect) Feb 24, 2024 1:03am
node-dca1 ❌ Failed (Inspect) Feb 24, 2024 1:03am
node-hrd9 ❌ Failed (Inspect) Feb 24, 2024 1:03am

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