USN-1757-1: Django vulnerabilities
7 March 2013
Several security issues were fixed in Django.
Releases
Packages
- python-django - High-level Python web development framework
Details
James Kettle discovered that Django did not properly filter the Host HTTP
header when processing certain requests. An attacker could exploit this to
generate and display arbitrary URLs to users. Although this issue had been
previously addressed in USN-1632-1, this update adds additional hardening
measures to host header validation. This update also adds a new
ALLOWED_HOSTS setting that can be set to a list of acceptable values for
headers. (CVE-2012-4520)
Orange Tsai discovered that Django incorrectly performed permission checks
when displaying the history view in the admin interface. An administrator
could use this flaw to view the history of any object, regardless of
intended permissions. (CVE-2013-0305)
It was discovered that Django incorrectly handled a large number of forms
when generating formsets. An attacker could use this flaw to cause Django
to consume memory, resulting in a denial of service. (CVE-2013-0306)
It was discovered that Django incorrectly deserialized XML. An attacker
could use this flaw to perform entity-expansion and external-entity/DTD
attacks. This updated modified Django behaviour to no longer allow DTDs,
perform entity expansion, or fetch external entities/DTDs. (CVE-2013-1664,
CVE-2013-1665)
Update instructions
The problem can be corrected by updating your system to the following package versions:
Ubuntu 12.10
Ubuntu 12.04
Ubuntu 11.10
Ubuntu 10.04
In general, a standard system update will make all the necessary changes.
Related notices
- USN-1632-1: python-django
- USN-1731-1: cinder, python-cinder
- USN-1730-1: python-keystone, keystone
- USN-1734-1: python-nova, nova