Django before 1.8.x before 1.8.16, 1.9.x before 1.9.11, and 1.10.x before 1.10.3, when settings.DEBUG is True, allow remote attackers to conduct DNS rebinding attacks by leveraging failure to validate the HTTP Host header against settings.ALLOWED_HOSTS.

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - python-django: DNS rebinding vulnerability when 'DEBUG=True' (CVE-2016-9014)

  - Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect     regular expression, which allows remote attackers to inject arbitrary headers and conduct HTTP response     splitting attacks via a newline character in an (1) email message to the EmailValidator, a (2) URL to the     URLValidator, or unspecified vectors to the (3) validate_ipv4_address or (4) validate_slug validator.
    (CVE-2015-5144)

  - 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. (CVE-2017-7233)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

This plugin has been deprecated as it does not adhere to established standards for this style of check.

This update for python3-Django to version 1.18.18 fixes multiple issues. Security issues fixed :

  - CVE-2018-7537: Fixed catastrophic backtracking in     django.utils.text.Truncator. (bsc#1083305)

  - CVE-2018-7536: Fixed catastrophic backtracking in urlize     and urlizetrunc template filters (bsc#1083304).

  - CVE-2016-7401: CSRF protection bypass on a site with     Google Analytics (bsc#1001374).

  - CVE-2016-2513: User enumeration through timing     difference on password hasher work factor upgrade     (bsc#968000).

  - CVE-2016-2512: Fixed malicious redirect and possible XSS     attack via user-supplied redirect URLs containing basic     auth (bsc#967999).

  - CVE-2016-9013: User with hardcoded password created when     running tests on Oracle (bsc#1008050).

  - CVE-2016-9014: DNS rebinding vulnerability when     DEBUG=True (bsc#1008047).

  - CVE-2017-7234: Open redirect vulnerability in     django.views.static.serve() (bsc#1031451).

  - CVE-2017-7233: Open redirect and possible XSS attack via     user-supplied numeric redirect URLs (bsc#1031450).

  - CVE-2017-12794: Fixed XSS possibility in traceback     section of technical 500 debug page (bsc#1056284)

This update for python-Django to version 1.18.18 fixes multiple issues. Security issues fixed :

  - CVE-2018-7537: Fixed catastrophic backtracking in     django.utils.text.Truncator. (bsc#1083305)

  - CVE-2018-7536: Fixed catastrophic backtracking in urlize     and urlizetrunc template filters (bsc#1083304).

  - CVE-2016-7401: CSRF protection bypass on a site with     Google Analytics (bsc#1001374).

  - CVE-2016-2513: User enumeration through timing     difference on password hasher work factor upgrade     (bsc#968000).

  - CVE-2016-2512: Fixed malicious redirect and possible XSS     attack via user-supplied redirect URLs containing basic     auth (bsc#967999).

  - CVE-2016-9013: User with hardcoded password created when     running tests on Oracle (bsc#1008050).

  - CVE-2016-9014: DNS rebinding vulnerability when     DEBUG=True (bsc#1008047).

  - CVE-2017-7234: Open redirect vulnerability in     django.views.static.serve() (bsc#1031451).

  - CVE-2017-7233: Open redirect and possible XSS attack via     user-supplied numeric redirect URLs (bsc#1031450).

  - CVE-2017-12794: Fixed XSS possibility in traceback     section of technical 500 debug page (bsc#1056284)

Several vulnerabilities were discovered in Django, a high-level Python web development framework. The Common Vulnerabilities and Exposures project identifies the following problems :

  - CVE-2016-9013     Marti Raudsepp reported that a user with a hard-coded     password is created when running tests with an Oracle     database.

  - CVE-2016-9014     Aymeric Augustin discovered that Django does not     properly validate the Host header against     settings.ALLOWED_HOSTS when the debug setting is     enabled. A remote attacker can take advantage of this     flaw to perform DNS rebinding attacks.

  - CVE-2017-7233     It was discovered that is_safe_url() does not properly     handle certain numeric URLs as safe. A remote attacker     can take advantage of this flaw to perform XSS attacks     or to use a Django server as an open redirect.

  - CVE-2017-7234     Phithon from Chaitin Tech discovered an open redirect     vulnerability in the django.views.static.serve() view.
    Note that this view is not intended for production use.

Security fix for CVE-2016-9013, CVE-2016-9014

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The Django project reports :

Today the Django team released Django 1.10.3, Django 1.9.11, and 1.8.16. These releases addresses two security issues detailed below.
We encourage all users of Django to upgrade as soon as possible.

- User with hard-coded password created when running tests on Oracle

- DNS rebinding vulnerability when DEBUG=True

The remote Ubuntu 14.04 LTS / 16.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-3115-1 advisory.

    Marti Raudsepp discovered that Django incorrectly used a hardcoded password when running tests on an     Oracle database. A remote attacker could possibly connect to the database while the tests are running and     prevent the test user with the hardcoded password from being removed. (CVE-2016-9013)

    Aymeric Augustin discovered that Django incorrectly validated hosts when being run with the debug setting     enabled. A remote attacker could possibly use this issue to perform DNS rebinding attacks. (CVE-2016-9014)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
198748	RHEL 6 : django (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	high
195464	RHEL 6 : python-django (Unpatched Vulnerability) (deprecated)	Nessus	Red Hat Local Security Checks	high
108641	openSUSE Security Update : python3-Django (openSUSE-2018-318)	Nessus	SuSE Local Security Checks	critical
108640	openSUSE Security Update : python-Django (openSUSE-2018-317)	Nessus	SuSE Local Security Checks	critical
99695	Debian DSA-3835-1 : python-django - security update	Nessus	Debian Local Security Checks	critical
95015	Fedora 25 : python-django (2016-d4571bf555)	Nessus	Fedora Local Security Checks	critical
94795	Fedora 24 : python-django (2016-3eb5a55123)	Nessus	Fedora Local Security Checks	critical
94494	FreeBSD : django -- multiple vulnerabilities (cb116651-79db-4c09-93a2-c38f9df46724)	Nessus	FreeBSD Local Security Checks	critical
94464	Ubuntu 14.04 LTS / 16.04 LTS : Django vulnerabilities (USN-3115-1)	Nessus	Ubuntu Local Security Checks	critical

Detections

Analytics

CVE-2016-9014

high

Tenable Plugins

high

high

critical

critical

critical

critical

critical

critical

critical