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] Security upgrade django from 3.2.14 to 3.2.16 #1076

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

Conversation

Romulus10
Copy link
Collaborator

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
s3transfer 0.4.2 requires botocore, which is not installed.
pyqldb 3.2.2 requires amazon.ion, which is not installed.
pyqldb 3.2.2 requires ionhash, which is not installed.
pyqldb 3.2.2 requires botocore, which is not installed.
django-rest-swagger 2.2.0 requires djangorestframework, which is not installed.
django-redis-sessions 0.6.2 requires redis, which is not installed.
django-pymemcache 1.0.0 has requirement Django>=2.2, but you have Django 1.11.29.
django-elastipymemcache 2.0.4 has requirement Django>=2.2, but you have Django 1.11.29.
coreschema 0.0.4 requires jinja2, which is not installed.
coreapi 2.3.3 requires uritemplate, which is not installed.
click-repl 0.2.0 requires prompt-toolkit, which is not installed.
boto3 1.17.112 requires botocore, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 564/1000
Why? Has a fix available, CVSS 7
Reflected File Download (RFD)
SNYK-PYTHON-DJANGO-2968205
django:
3.2.14 -> 3.2.16
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-3039675
django:
3.2.14 -> 3.2.16
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:

🦉 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
Development

Successfully merging this pull request may close these issues.

2 participants