Security releases issued

Posted by Tim Graham on January 13, 2015

Today the Django team is issuing multiple releases -- Django 1.4.18, Django 1.6.10, and Django 1.7.3 -- as part of our security process. These releases are now available on PyPI and our download page.

These releases address several security issues. We encourage all users of Django to upgrade as soon as possible.

Issue: WSGI header spoofing via underscore/dash conflation

When HTTP headers are placed into the WSGI environ, they are normalized by converting to uppercase, converting all dashes to underscores, and prepending HTTP_. For instance, a header X-Auth-User would become HTTP_X_AUTH_USER in the WSGI environ (and thus also in Django's request.META dictionary).

Unfortunately, this means that the WSGI environ cannot distinguish between headers containing dashes and headers containing underscores: X-Auth-User and X-Auth_User both become HTTP_X_AUTH_USER. This means that if a header is used in a security-sensitive way (for instance, passing authentication information along from a front-end proxy), even if the proxy carefully strips any incoming value for X-Auth-User, an attacker may be able to provide an X-Auth_User header (with underscore) and bypass this protection.

In order to prevent such attacks, both Nginx and Apache 2.4+ strip all headers containing underscores from incoming requests by default. Django's built-in development server now does the same. Django's development server is not recommended for production use, but matching the behavior of common production servers reduces the surface area for behavior changes during deployment.

This issue has been assigned the CVE identifier CVE-2015-0219.

Thanks to Jedediah Smith for reporting the issue.

Issue: Mitigated possible XSS attack via user-supplied redirect URLs

Django relies on user input in some cases (e.g. django.contrib.auth.views.login() and i18n) to redirect the user to an "on success" URL. The security checks for these redirects (namely django.util.http.is_safe_url()) didn't strip leading whitespace on the tested URL and as such considered URLs like \njavascript:... safe. If a developer relied on is_safe_url() to provide safe redirect targets and put such a URL into a link, they could suffer from a XSS attack. This bug doesn't affect Django currently, since we only put this URL into the Location response header and browsers seem to ignore JavaScript there.

This issue has been assigned the CVE identifier CVE-2015-0220.

Thanks to Mikko Ohtamaa for reporting the issue.

Issue: Denial-of-service attack against django.views.static.serve

In older versions of Django, the django.views.static.serve() view read the files it served one line at a time. Therefore, a big file with no newlines would result in memory usage equal to the size of that file. An attacker could exploit this and launch a denial-of-service attack by simultaneously requesting many large files. This view now reads the file in chunks to prevent large memory usage.

Note, however, that this view has always carried a warning that it is not hardened for production use and should be used only as a development aid. Now may be a good time to audit your project and serve your files in production using a real front-end web server if you are not doing so.

This issue has been assigned the CVE identifier CVE-2015-0221.

Thanks Alex Gaynor for reporting the issue.

Issue: Database denial-of-service with ModelMultipleChoiceField

Given a form that uses ModelMultipleChoiceField and show_hidden_initial=True (not a documented API), it was possible for a user to cause an unreasonable number of SQL queries by submitting duplicate values for the field's data. The validation logic in ModelMultipleChoiceField now deduplicates submitted values to address this issue.

This issue has been assigned the CVE identifier CVE-2015-0222.

Thanks Keryn Knight for reporting the issue.

Affected versions

  • Django master development branch (currently at pre-alpha status) (except the serve() denial of service issue)
  • Django 1.7
  • Django 1.6
  • Django 1.4 [Long-term support] (except the ModelMultipleChoiceField issue)

Per our supported versions policy, Django 1.5 is no longer receiving security updates.


Patches have been applied to Django's master development branch and to the 1.4, 1.6 and 1.7 release branches, which resolve the issues described above. The patches may be obtained directly from the following changesets:

On the development master branch:

On the 1.7 release branch:

On the 1.6 release branch:

On the 1.4 release branch:

The following new releases have been issued:

The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.

General notes regarding security reporting

As always, we ask that potential security issues be reported via private email to, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.

Back to Top