CVE-2010-4535: Improper date handling in Django
(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.
References
- bugzilla.redhat.com/show_bug.cgi?id=665373
- github.com/advisories/GHSA-7wph-fc4w-wqp2
- github.com/django/django/commit/7f8dd9cbac074389af8d8fd235bf2cb657227b9a
- github.com/django/django/commit/d5d8942a160685c403d381a279e72e09de5489a9
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-29.yaml
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-9.yaml
- nvd.nist.gov/vuln/detail/CVE-2010-4535
- web.archive.org/web/20200228193349/http://www.securityfocus.com/bid/45563
Code Behaviors & Features
Detect and mitigate CVE-2010-4535 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →