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 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 | |
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 | |
Canonical Ubuntu Linux | =10.04 | |
Canonical Ubuntu Linux | =11.10 | |
Canonical Ubuntu Linux | =12.04 | |
Canonical Ubuntu Linux | =12.10 | |
pip/Django | >=1.4<1.4.4 | 1.4.4 |
pip/Django | >=1.3<1.3.6 | 1.3.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.