Django security releases issued: 1.11.5 and 1.10.8
In accordance with our security release policy, the Django team is issuing Django 1.11.5 and Django 1.10.8. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
CVE-2017-12794: Possible XSS in traceback section of technical 500 debug page
In older versions, 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.
Thanks Charles Bideau for reporting this issue.
Affected supported versions
- Django master development branch
- Django 1.11
- Django 1.10
Per our supported versions policy, Django 1.9 is no longer supported. Django 1.8 is unaffected.
Patches to resolve the issues have been applied to Django's master development branch and the 1.11 and 1.10 release branches. The patches may be obtained from the following changesets:
- On the development master branch
- On the 1.11 release branch
- On the 1.10 release branch
The following releases have been issued:
- Django 1.11.5 (download Django 1.11.5 | 1.11.5 checksums)
- Django 1.10.8 (download Django 1.10.8 | 1.10.8 checksums)
The PGP key ID used for these releases is Tim Graham: 1E8ABDC773EDE252.
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email to firstname.lastname@example.org, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.