First published: Fri Feb 22 2013(Updated: )
The administrative interface for Django 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 does not check permissions for the history view, which allows remote authenticated administrators to obtain sensitive object history information.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/python-django | 1:1.11.29-1~deb10u1 1:1.11.29-1+deb10u9 2:2.2.28-1~deb11u1 2:2.2.28-1~deb11u2 3:3.2.19-1 3:3.2.19-1+deb12u1 3:3.2.20-1.1 3:3.2.21-1 | |
pip/Django | >=1.4<1.4.4 | 1.4.4 |
pip/Django | >=1.3<1.3.6 | 1.3.6 |
djangoproject Django | =1.3 | |
djangoproject Django | =1.3-alpha1 | |
djangoproject Django | =1.3-beta1 | |
djangoproject Django | =1.3.1 | |
djangoproject Django | =1.3.2 | |
djangoproject Django | =1.3.3 | |
djangoproject Django | =1.4 | |
djangoproject Django | =1.4-alpha | |
djangoproject Django | =1.4-beta | |
djangoproject Django | =1.4.1 | |
djangoproject Django | =1.4.2 | |
djangoproject Django | =1.5-alpha | |
djangoproject Django | =1.5-beta | |
Ubuntu Linux | =10.04 | |
Ubuntu Linux | =11.10 | |
Ubuntu Linux | =12.04 | |
Ubuntu Linux | =12.10 | |
Ubuntu | =10.04 | |
Ubuntu | =11.10 | |
Ubuntu | =12.04 | |
Ubuntu | =12.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0305 has a high severity rating due to its potential to expose sensitive object history information to unauthorized users.
To fix CVE-2013-0305, update Django to version 1.3.6 or higher for the 1.3.x series, or to 1.4.4 or higher for the 1.4.x series.
Django versions 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 are affected by CVE-2013-0305.
CVE-2013-0305 allows remote authenticated administrators to access sensitive object history information without proper permission checks.
CVE-2013-0305 affects Django installations across multiple operating systems that use the vulnerable Django versions.