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 7 vulnerabilities #62

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

Conversation

adamlaska
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
xml2rfc 3.21.0 requires platformdirs, which is not installed.
xml2rfc 3.21.0 requires configargparse, which is not installed.
xml2rfc 3.21.0 requires google-i18n-address, which is not installed.
xml2rfc 3.21.0 requires intervaltree, which is not installed.
xml2rfc 3.21.0 requires jinja2, which is not installed.
xml2rfc 3.21.0 requires pycountry, which is not installed.
scout-apm 2.26.1 has requirement urllib3[secure]<2; python_version >= "3.5", but you have urllib3 2.0.7.
django-vite 3.0.4 has requirement Django>=3.2, but you have Django 2.2.28.
django-csp 3.8 has requirement Django>=3.2, but you have Django 2.2.28.
django-cors-headers 4.1.0 has requirement Django>=3.2, but you have Django 2.2.28.
celery 5.3.0 requires kombu, which is not installed.

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 524/1000
Why? Has a fix available, CVSS 6.2
Resource Exhaustion
SNYK-PYTHON-IDNA-6597975
idna:
2.10 -> 3.7
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.27.1 -> 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:
40.5.0 -> 65.5.1
No No Known Exploit
medium severity 633/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.8
Injection
SNYK-PYTHON-TQDM-6807582
tqdm:
4.64.1 -> 4.66.3
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
HTTP Request Smuggling
SNYK-PYTHON-WAITRESS-2428349
waitress:
1.4.4 -> 2.1.1
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:

🦉 Resource Exhaustion

Copy link

google-cla bot commented May 16, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants