Skip to content

[Snyk] Security upgrade django from 1.6.11 to 2.2.18 - #9

Open
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-d5eb12d7273e585726da2475b3f8b874
Open

[Snyk] Security upgrade django from 1.6.11 to 2.2.18#9
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-d5eb12d7273e585726da2475b3f8b874

Conversation

@snyk-bot

@snyk-bot snyk-bot commented Sep 7, 2021

Copy link
Copy Markdown

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 
Cactus 3.3.3 has requirement Django<1.7,>=1.6, but you have Django 1.11.29.

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:
1.6.11 -> 2.2.18
No No Known Exploit
low severity 379/1000
Why? Has a fix available, CVSS 3.3		 Directory Traversal
SNYK-PYTHON-DJANGO-1279042		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3		 HTTP Header Injection
SNYK-PYTHON-DJANGO-1290072		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5		 Directory Traversal
SNYK-PYTHON-DJANGO-1298665		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-40332		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3		 HTTP Response Splitting
SNYK-PYTHON-DJANGO-40333		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-40339		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3		 Denial of Service (DoS)
SNYK-PYTHON-DJANGO-40340		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3		 Information Exposure
SNYK-PYTHON-DJANGO-40359		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 584/1000
Why? Has a fix available, CVSS 7.4		 Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-40382		 django:
1.6.11 -> 2.2.18
No No Known Exploit
low severity 369/1000
Why? Has a fix available, CVSS 3.1		 Timing Attack
SNYK-PYTHON-DJANGO-40383		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 626/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.1		 Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-40403		 django:
1.6.11 -> 2.2.18
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5		 Cross-site Request Forgery (CSRF)
SNYK-PYTHON-DJANGO-40434		 django:
1.6.11 -> 2.2.18
No No Known Exploit
critical severity 704/1000
Why? Has a fix available, CVSS 9.8		 Use of hardcoded DB password
SNYK-PYTHON-DJANGO-40439		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 619/1000
Why? Has a fix available, CVSS 8.1		 DNS Rebinding
SNYK-PYTHON-DJANGO-40440		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1		 Open Redirect
SNYK-PYTHON-DJANGO-40460		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1		 Open Redirect
SNYK-PYTHON-DJANGO-40461		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1		 Open Redirect
SNYK-PYTHON-DJANGO-42178		 django:
1.6.11 -> 2.2.18
No No Known Exploit
high severity 594/1000
Why? Has a fix available, CVSS 7.6		 SQL Injection
SNYK-PYTHON-DJANGO-559326		 django:
1.6.11 -> 2.2.18
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3		 Content Spoofing
SNYK-PYTHON-DJANGO-72888		 django:
1.6.11 -> 2.2.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 effected 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

@snyk-bot
fix: requirements.txt to reduce vulnerabilities
0422ec2 
The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1066259
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1279042
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1290072
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1298665
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40332
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40333
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40339
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40340
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40359
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40382
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40383
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40403
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40434
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40439
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40440
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40460
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-40461
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-42178
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-559326
- https://snyk.io/vuln/SNYK-PYTHON-DJANGO-72888
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@snyk-bot