First published: Mon Jan 10 2011(Updated: )
The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Django | >=1.2<1.2.4 | 1.2.4 |
pip/django | <1.1.3 | 1.1.3 |
Django | <=1.1.2 | |
Django | =0.91 | |
Django | =0.95 | |
Django | =0.95.1 | |
Django | =0.96 | |
Django | =1.0 | |
Django | =1.0.1 | |
Django | =1.0.2 | |
Django | =1.1 | |
Django | =1.1.0 | |
Django | =1.2 | |
Django | =1.2.1 | |
Django | =1.2.2 | |
Django | =1.2.3 | |
Django | =1.3-alpha1 | |
Django | =1.3-alpha2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4535 has a medium severity rating due to its potential for denial of service through resource consumption.
To fix CVE-2010-4535, upgrade to Django version 1.2.4 or later, or to 1.1.3 or later.
CVE-2010-4535 affects Django versions prior to 1.1.3, 1.2.4, and 1.3 beta 1.
CVE-2010-4535 is a denial of service vulnerability related to password reset functionality.
Remote attackers can exploit CVE-2010-4535 by sending specially crafted URLs to trigger the vulnerability.