[Snyk] Security upgrade django from 1.10 to 2.2.18

[snyk-bot]

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:
  • testserver/requirements.txt

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	369/1000 Why? Has a fix available, CVSS 3.1	Directory Traversal SNYK-PYTHON-DJANGO-1066259	django: 1.10 -> 2.2.18	No	No Known Exploit
	379/1000 Why? Has a fix available, CVSS 3.3	Directory Traversal SNYK-PYTHON-DJANGO-1279042	django: 1.10 -> 2.2.18	No	No Known Exploit
	579/1000 Why? Has a fix available, CVSS 7.3	HTTP Header Injection SNYK-PYTHON-DJANGO-1290072	django: 1.10 -> 2.2.18	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Directory Traversal SNYK-PYTHON-DJANGO-1298665	django: 1.10 -> 2.2.18	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	Use of hardcoded DB password SNYK-PYTHON-DJANGO-40439	django: 1.10 -> 2.2.18	No	No Known Exploit
	619/1000 Why? Has a fix available, CVSS 8.1	DNS Rebinding SNYK-PYTHON-DJANGO-40440	django: 1.10 -> 2.2.18	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Open Redirect SNYK-PYTHON-DJANGO-40460	django: 1.10 -> 2.2.18	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Open Redirect SNYK-PYTHON-DJANGO-40461	django: 1.10 -> 2.2.18	No	No Known Exploit
	626/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 6.1	Cross-site Scripting (XSS) SNYK-PYTHON-DJANGO-40626	django: 1.10 -> 2.2.18	No	Proof of Concept
	479/1000 Why? Has a fix available, CVSS 5.3	Information Exposure SNYK-PYTHON-DJANGO-40778	django: 1.10 -> 2.2.18	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-DJANGO-40779	django: 1.10 -> 2.2.18	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Open Redirect SNYK-PYTHON-DJANGO-42178	django: 1.10 -> 2.2.18	No	No Known Exploit
	594/1000 Why? Has a fix available, CVSS 7.6	SQL Injection SNYK-PYTHON-DJANGO-559326	django: 1.10 -> 2.2.18	No	No Known Exploit
	429/1000 Why? Has a fix available, CVSS 4.3	Content Spoofing SNYK-PYTHON-DJANGO-72888	django: 1.10 -> 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