First published: Thu Dec 23 2010(Updated: )
Description of problem: <a href="http://www.djangoproject.com/weblog/2010/dec/22/security/">http://www.djangoproject.com/weblog/2010/dec/22/security/</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | =0.95 | |
Djangoproject Django | =1.0 | |
Djangoproject Django | =1.0.1 | |
Djangoproject Django | =1.1 | |
Djangoproject Django | =0.91 | |
Djangoproject Django | =1.0.2 | |
Djangoproject Django | =0.95.1 | |
Djangoproject Django | =0.96 | |
Djangoproject Django | <=1.1.2 | |
Djangoproject Django | =1.1.0 | |
Djangoproject Django | =1.2.1 | |
Djangoproject Django | =1.2.3 | |
Djangoproject Django | =1.2 | |
Djangoproject Django | =1.2.2 | |
Djangoproject Django | =1.3-alpha1 | |
Djangoproject Django | =1.3-alpha2 | |
pip/Django | >=1.2<1.2.4 | 1.2.4 |
pip/django | <1.1.3 | 1.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4534 is classified as a medium severity vulnerability.
To remediate CVE-2010-4534, upgrade Django to version 1.1.3 or later, or 1.2.4 or later.
CVE-2010-4534 affects Django versions up to 1.1.2, 1.2.3, and all earlier versions.
CVE-2010-4534 is an information leakage vulnerability in the administrative interface of Django.
The recommended solution for CVE-2010-4534 is upgrading to a patched version rather than relying on a workaround.