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.

References

• https://nvd.nist.gov/vuln/detail/CVE-2010-4535
• https://bugzilla.redhat.com/show_bug.cgi?id=665373
• GHSA-7wph-fc4w-wqp2
• http://code.djangoproject.com/changeset/15032
• http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html
• http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html
• http://secunia.com/advisories/42715
• http://secunia.com/advisories/42827
• http://secunia.com/advisories/42913
• http://www.openwall.com/lists/oss-security/2010/12/23/4
• http://www.openwall.com/lists/oss-security/2011/01/03/5
• http://www.securityfocus.com/bid/45563
• http://www.ubuntu.com/usn/USN-1040-1
• http://www.vupen.com/english/advisories/2011/0048
• http://www.vupen.com/english/advisories/2011/0098
• django/django@7f8dd9c
• django/django@d5d8942
• http://www.djangoproject.com/weblog/2010/dec/22/security