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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
http://code.djangoproject.com/changeset/15032 | patch |
http://www.openwall.com/lists/oss-security/2010/12/23/4 | patch mailing list |
http://www.ubuntu.com/usn/USN-1040-1 | vendor advisory |
http://www.securityfocus.com/bid/45563 | vdb entry |
http://www.openwall.com/lists/oss-security/2011/01/03/5 | patch mailing list |
http://secunia.com/advisories/42913 | third party advisory |
http://www.vupen.com/english/advisories/2011/0048 | vdb entry |
http://www.vupen.com/english/advisories/2011/0098 | vdb entry |
http://www.djangoproject.com/weblog/2010/dec/22/security/ | patch vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=665373 | patch |
http://secunia.com/advisories/42715 | third party advisory vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html | vendor advisory |
http://secunia.com/advisories/42827 | third party advisory |