The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a denial of service (CPU consumption) by unloading a multiple files with the same name.

This update address an issue with reverse() generating external URLs;
a denial of service involving file uploads; a potential session hijacking issue in the remote-user middleware; and a data leak in the administrative interface.

http://www.freexian.com/services/debian-lts.html

CVE-2014-0480

Django includes the helper function django.core.urlresolvers.reverse, typically used to generate a URL from a reference to a view function or URL pattern name. However, when presented with input beginning with two forward-slash characters (//), reverse() could generate scheme-relative URLs to other hosts, allowing an attacker who is aware of unsafe use of reverse() (i.e., in a situation where an end user can control the target of a redirect, to take a common example) to generate links to sites of their choice, enabling phishing and other attacks.

To remedy this, URL reversing now ensures that no URL starts with two slashes (//), replacing the second slash with its URL encoded counterpart (%2F). This approach ensures that semantics stay the same, while making the URL relative to the domain and not to the scheme.

CVE-2014-0481

In the default configuration, when Django's file upload handling system is presented with a file that would have the same on-disk path and name as an existing file, it attempts to generate a new unique filename by appending an underscore and an integer to the end of the (as stored on disk) filename, incrementing the integer (i.e., _1, _2, etc.) until it has generated a name which does not conflict with any existing file.

An attacker with knowledge of this can exploit the sequential behavior of filename generation by uploading many tiny files which all share a filename; Django will, in processing them, generate ever-increasing numbers of os.stat() calls as it attempts to generate a unique filename. As a result, even a relatively small number of such uploads can significantly degrade performance.

To remedy this, Django's file-upload system will no longer use sequential integer names to avoid filename conflicts on disk; instead, a short random alphanumeric string will be appended, removing the ability to reliably generate many repeatedly-conflicting filenames.

CVE-2014-0482

Django provides a middleware -- django.contrib.auth.middleware.RemoteUserMiddleware -- and an authentication backend, django.contrib.auth.backends.RemoteUserBackend, which use the REMOTE_USER header for authentication purposes.

In some circumstances, use of this middleware and backend could result in one user receiving another user's session, if a change to the REMOTE_USER header occurred without corresponding logout/login actions.

To remedy this, the middleware will now ensure that a change to REMOTE_USER without an explicit logout will force a logout and subsequent login prior to accepting the new REMOTE_USER.

CVE-2014-0483

Django's administrative interface, django.contrib.admin, offers a feature whereby related objects can be displayed for selection in a popup window. The mechanism for this relies on placing values in the URL and querystring which specify the related model to display and the field through which the relationship is implemented. This mechanism does perform permission checks at the level of the model class as a whole.

This mechanism did not, however, verify that the specified field actually represents a relationship between models.
Thus a user with access to the admin interface, and with sufficient knowledge of model structure and the appropriate URLs, could construct popup views which would display the values of non-relationship fields, including fields the application developer had not intended to expose in such a fashion.

To remedy this, the admin interface will now, in addition to its normal permission checks, verify that the specified field does indeed represent a relationship, to a model registered with the admin, and will raise an exception if either condition is not true.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-201412-22 (Django: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Django. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker may be able to create a Denial of Service condition,       obtain sensitive information, or hijack web sessions.
  Workaround :

    There is no known workaround at this time.

Update to latest stable release

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

update to latest stable release

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

The remote Ubuntu 14.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-2347-1 advisory.

    Florian Apolloner discovered that Django incorrectly validated URLs. A remote attacker could use this     issue to conduct phishing attacks. (CVE-2014-0480)

    David Wilson discovered that Django incorrectly handled file name generation. A remote attacker could use     this issue to cause Django to consume resources, resulting in a denial of service. (CVE-2014-0481)

    David Greisen discovered that Django incorrectly handled certain headers in     contrib.auth.middleware.RemoteUserMiddleware. A remote authenticated user could use this issue to hijack     web sessions. (CVE-2014-0482)

    Collin Anderson discovered that Django incorrectly checked if a field represented a relationship between     models in the administrative interface. A remote authenticated user could use this issue to possibly     obtain sensitive information. (CVE-2014-0483)

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.

Python Django was updated to fix security issues and bugs.

Update to version 1.4.15 on openSUSE 12.3 :

  + Prevented reverse() from generating URLs pointing to     other hosts to prevent phishing attacks (bnc#893087,     CVE-2014-0480)

  + Removed O(n) algorithm when uploading duplicate file     names to fix file upload denial of service (bnc#893088,     CVE-2014-0481)

  + Modified RemoteUserMiddleware to logout on REMOTE_USE     change to prevent session hijacking (bnc#893089,     CVE-2014-0482)

  + Prevented data leakage in contrib.admin via query string     manipulation (bnc#893090, CVE-2014-0483)

  + Fixed: Caches may incorrectly be allowed to store and     serve private data (bnc#877993, CVE-2014-1418)

  + Fixed: Malformed redirect URLs from user input not     correctly validated (bnc#878641, CVE-2014-3730)

  + Fixed queries that may return unexpected results on     MySQL due to typecasting (bnc#874956, CVE-2014-0474)

  + Prevented leaking the CSRF token through caching     (bnc#874955, CVE-2014-0473)

  + Fixed a remote code execution vulnerability in URL     reversing (bnc#874950, CVE-2014-0472)

Update to version 1.5.10 on openSUSE 13.1 :

  + Prevented reverse() from generating URLs pointing to     other hosts to prevent phishing attacks (bnc#893087,     CVE-2014-0480)

  + Removed O(n) algorithm when uploading duplicate file     names to fix file upload denial of service (bnc#893088,     CVE-2014-0481)

  + Modified RemoteUserMiddleware to logout on REMOTE_USE     change to prevent session hijacking (bnc#893089,     CVE-2014-0482)

  + Prevented data leakage in contrib.admin via query string     manipulation (bnc#893090, CVE-2014-0483)

  - Update to version 1.5.8 :

  + Fixed: Caches may incorrectly be allowed to store and     serve private data (bnc#877993, CVE-2014-1418)

  + Fixed: Malformed redirect URLs from user input not     correctly validated (bnc#878641, CVE-2014-3730)

  + Fixed queries that may return unexpected results on     MySQL due to typecasting (bnc#874956, CVE-2014-0474)

  + Prevented leaking the CSRF token through caching     (bnc#874955, CVE-2014-0473)

  + Fixed a remote code execution vulnerability in URL     reversing (bnc#874950, CVE-2014-0472)

Updated python-django packages fix security vulnerabilities :

These releases address an issue with reverse() generating external URLs (CVE-2014-0480); a denial of service involving file uploads (CVE-2014-0481); a potential session hijacking issue in the remote-user middleware (CVE-2014-0482); and a data leak in the administrative interface (CVE-2014-0483).

Security fix for CVE-2014-0480, CVE-2014-0481, CVE-2014-0482, CVE-2014-0483

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

update to 1.5.9 fixing CVE-2014-3473 CVE-2014-3474 CVE-2014-3475

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

update to 1.4.14 fixing CVE-2014-0480 CVE-2014-0481 CVE-2014-0482, CVE-2014-0483

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

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

  - CVE-2014-0480     Florian Apolloner discovered that in certain situations,     URL reversing could generate scheme-relative URLs which     could unexpectedly redirect a user to a different host,     leading to phishing attacks.

  - CVE-2014-0481     David Wilson reported a file upload denial of service     vulnerability. Django's file upload handling in its     default configuration may degrade to producing a huge     number of `os.stat()` system calls when a duplicate     filename is uploaded. A remote attacker with the ability     to upload files can cause poor performance in the upload     handler, eventually causing it to become very slow.

  - CVE-2014-0482     David Greisen discovered that under some circumstances,     the use of the RemoteUserMiddleware middleware and the     RemoteUserBackend authentication backend could result in     one user receiving another user's session, if a change     to the REMOTE_USER header occurred without corresponding     logout/login actions.

  - CVE-2014-0483     Collin Anderson discovered that it is possible to reveal     any field's data by modifying the 'popup' and 'to_field'     parameters of the query string on an admin change form     page. A user with access to the admin interface, and     with sufficient knowledge of model structure and the     appropriate URLs, could construct popup views which     would display the values of non-relationship fields,     including fields the application developer had not     intended to expose in such a fashion.

The Django project reports :

These releases address an issue with reverse() generating external URLs; a denial of service involving file uploads; a potential session hijacking issue in the remote-user middleware; and a data leak in the administrative interface. We encourage all users of Django to upgrade as soon as possible.

ID	Name	Product	Family	Severity
82210	Debian DLA-65-1 : python-django security update	Nessus	Debian Local Security Checks	medium
79975	GLSA-201412-22 : Django: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium
79646	Fedora 19 : python-django14-1.4.16-1.fc19 (2014-15307)	Nessus	Fedora Local Security Checks	medium
79645	Fedora 20 : python-django14-1.4.16-1.fc20 (2014-15266)	Nessus	Fedora Local Security Checks	medium
77725	Ubuntu 14.04 LTS : Django vulnerabilities (USN-2347-1)	Nessus	Ubuntu Local Security Checks	medium
77718	openSUSE Security Update : python-django (openSUSE-SU-2014:1132-1)	Nessus	SuSE Local Security Checks	critical
77658	Mandriva Linux Security Advisory : python-django (MDVSA-2014:179)	Nessus	Mandriva Local Security Checks	medium
77614	Fedora 20 : python-django15-1.5.9-1.fc20 (2014-9866)	Nessus	Fedora Local Security Checks	medium
77592	Fedora 19 : python-django-1.5.9-1.fc19 (2014-9791)	Nessus	Fedora Local Security Checks	medium
77591	Fedora 20 : python-django14-1.4.14-1.fc20 (2014-9788)	Nessus	Fedora Local Security Checks	medium
77590	Fedora 20 : python-django-1.6.6-1.fc20 (2014-9771)	Nessus	Fedora Local Security Checks	medium
77344	Debian DSA-3010-1 : python-django - security update	Nessus	Debian Local Security Checks	medium
77315	FreeBSD : django -- multiple vulnerabilities (3c5579f7-294a-11e4-99f6-00e0814cab4e)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2014-0481

medium

Tenable Plugins

medium

medium

medium

medium

medium

critical

medium

medium

medium

medium

medium

medium

medium