[Security] Bump django from 1.10.4 to 2.1.7

[dependabot-preview]

Bumps django from 1.10.4 to 2.1.7. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Sonatype OSS Index.

[CVE-2017-12794] Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting")
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with "DEBUG = True" (which makes this page accessible) in your production settings.

Affected versions: <= 1.10.7, >= 1.10.0; <= 1.11.4, >= 1.11.0

Sourced from The Sonatype OSS Index.

[CVE-2017-7233] URL Redirection to Untrusted Site ("Open Redirect")
Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an "on success" URL. The security check for these redirects (namely django.utils.http.is_safe_url()) considered some numeric URLs "safe" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.

Affected versions: = 1.8.0-a1; <= 1.8.0-b2, >= 1.8.0-b1; = 1.8.0; = 1.8.0-c1; <= 1.8.17, >= 1.8.1; = 1.9.0-a1; = 1.9.0-b1; <= 1.9.0-rc2, >= 1.9.0-rc1; <= 1.9.12, >= 1.9.0; = 1.10.0-a1; = 1.10.0-b1; = 1.10.0-rc1; <= 1.10.6, >= 1.10.0

Sourced from The Sonatype OSS Index.

[CVE-2017-7234] URL Redirection to Untrusted Site ("Open Redirect")
A maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the django.views.static.serve() view could redirect to any other domain, aka an open redirect vulnerability.

Affected versions: = 1.8.0-a1; <= 1.8.0-b2, >= 1.8.0-b1; = 1.8.0; = 1.8.0-c1; <= 1.8.17, >= 1.8.1; = 1.9.0-a1; = 1.9.0-b1; <= 1.9.0-rc2, >= 1.9.0-rc1; <= 1.9.12, >= 1.9.0; = 1.10.0-a1; = 1.10.0-b1; = 1.10.0-rc1; <= 1.10.6, >= 1.10.0

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects django
In Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in django.views.defaults.page_not_found(), leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.

Affected versions: < 1.11.18

Sourced from The Sonatype OSS Index.

[CVE-2017-12794] Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting")
In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with "DEBUG = True" (which makes this page accessible) in your production settings.

Affected versions: >= 1.10.0, <= 1.10.7; >= 1.11.0, <= 1.11.4

Sourced from The Sonatype OSS Index.

[CVE-2017-7234] URL Redirection to Untrusted Site ("Open Redirect")
A maliciously crafted URL to a Django (1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18) site using the django.views.static.serve() view could redirect to any other domain, aka an open redirect vulnerability.

Affected versions: = 1.8.0-a1; >= 1.8.0-b1, <= 1.8.0-b2; = 1.8.0; = 1.8.0-c1; >= 1.8.1, <= 1.8.17; = 1.9.0-a1; = 1.9.0-b1; >= 1.9.0-rc1, <= 1.9.0-rc2; >= 1.9.0, <= 1.9.12; = 1.10.0-a1; = 1.10.0-b1; = 1.10.0-rc1; >= 1.10.0, <= 1.10.6

Sourced from The Sonatype OSS Index.

[CVE-2017-7233] URL Redirection to Untrusted Site ("Open Redirect")
Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an "on success" URL. The security check for these redirects (namely django.utils.http.is_safe_url()) considered some numeric URLs "safe" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.

Affected versions: = 1.8.0-a1; >= 1.8.0-b1, <= 1.8.0-b2; = 1.8.0; = 1.8.0-c1; >= 1.8.1, <= 1.8.17; = 1.9.0-a1; = 1.9.0-b1; >= 1.9.0-rc1, <= 1.9.0-rc2; >= 1.9.0, <= 1.9.12; = 1.10.0-a1; = 1.10.0-b1; = 1.10.0-rc1; >= 1.10.0, <= 1.10.6

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #65.