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 12 vulnerabilities #16

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

Conversation

evildevill
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:
    • requirements.txt
⚠️ Warning
pypiwin32 223 requires pywin32, which is not installed.
pylint 2.7.0 has requirement astroid==2.5.0, but you have astroid 2.4.2.

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:
2020.11.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:
2020.11.8 -> 2023.7.22
No No Known Exploit
high severity 655/1000
Why? Has a fix available, CVSS 8.6
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1727377
pillow:
8.0.1 -> 8.3.2
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYLINT-1089548
pylint:
2.6.0 -> 2.7.0
No No Known Exploit
high severity 630/1000
Why? Has a fix available, CVSS 8.1
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYLINT-609883
pylint:
2.6.0 -> 2.7.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.25.0 -> 2.31.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Timing Attack
SNYK-PYTHON-RSA-1038401
rsa:
4.6 -> 4.7
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
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Improper Certificate Validation
SNYK-PYTHON-URLLIB3-1085966
urllib3:
1.26.2 -> 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.26.2 -> 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.26.2 -> 1.26.18
No No Known Exploit
medium severity 496/1000
Why? Recently disclosed, Has a fix available, CVSS 4.2
Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-6002459
urllib3:
1.26.2 -> 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:

🦉 Regular Expression Denial of Service (ReDoS)

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