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 2.0.1 to 3.2.15 #558

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

Conversation

snyk-bot
Copy link

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:
    • packages/snyk-fix/test/acceptance/plugins/python/handlers/pip-requirements/update-dependencies/workspaces/app-with-already-fixed/expected-requirements.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
low severity 369/1000
Why? Has a fix available, CVSS 3.1
Directory Traversal
SNYK-PYTHON-DJANGO-1066259
django:
2.0.1 -> 3.2.15
No No Known Exploit
low severity 379/1000
Why? Has a fix available, CVSS 3.3
Directory Traversal
SNYK-PYTHON-DJANGO-1279042
django:
2.0.1 -> 3.2.15
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
HTTP Header Injection
SNYK-PYTHON-DJANGO-1290072
django:
2.0.1 -> 3.2.15
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Directory Traversal
SNYK-PYTHON-DJANGO-1298665
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Uncontrolled Memory Consumption
SNYK-PYTHON-DJANGO-173679
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Access Restriction Bypass
SNYK-PYTHON-DJANGO-2312875
django:
2.0.1 -> 3.2.15
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Directory Traversal
SNYK-PYTHON-DJANGO-2329158
django:
2.0.1 -> 3.2.15
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Information Exposure
SNYK-PYTHON-DJANGO-2329159
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2329160
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 424/1000
Why? Has a fix available, CVSS 4.2
Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021
django:
2.0.1 -> 3.2.15
No No Known Exploit
high severity 624/1000
Why? Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606966
django:
2.0.1 -> 3.2.15
No No Known Exploit
high severity 731/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606969
django:
2.0.1 -> 3.2.15
No Proof of Concept
critical severity 776/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.1
SQL Injection
SNYK-PYTHON-DJANGO-2940618
django:
2.0.1 -> 3.2.15
No Proof of Concept
high severity 564/1000
Why? Has a fix available, CVSS 7
Reflected File Download (RFD)
SNYK-PYTHON-DJANGO-2968205
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Information Exposure
SNYK-PYTHON-DJANGO-40778
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-DJANGO-40779
django:
2.0.1 -> 3.2.15
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Information Exposure
SNYK-PYTHON-DJANGO-42054
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Open Redirect
SNYK-PYTHON-DJANGO-42178
django:
2.0.1 -> 3.2.15
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Content Spoofing
SNYK-PYTHON-DJANGO-72888
django:
2.0.1 -> 3.2.15
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:

🦉 Open Redirect
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Information Exposure
🦉 More lessons are available in Snyk Learn

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