Vulnerabilities · 2009 · Djangoproject
CVE-2009-3695
Djangoproject Django vulnerability
Algorithmic complexity vulnerability in the forms library in Django 1.0 before 1.0.4 and 1.1 before 1.1.1 allows remote attackers to cause a denial of service (CPU consumption) via a crafted (1) EmailField (email address) or (2) URLField (URL) that triggers a large amount of backtracking in a regular expression.
Affected products
Django. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- secunia.com/advisories/36948 · Vendor Advisory
- secunia.com/advisories/36968 · Vendor Advisory
- www.djangoproject.com/weblog/2009/oct/09/security/ · Patch
- www.vupen.com/english/advisories/2009/2871 · Patch
- www.securityfocus.com/bid/36655 · Patch
- bugs.debian.org/cgi-bin/bugreport.cgi?bug=550457
- groups.google.com/group/django-users/browse_thread/thread/15df9e45118dfc51/
- www.debian.org/security/2009/dsa-1905
- nvd.nist.gov/vuln/detail/CVE-2009-3695
- cve.org/CVERecord?id=CVE-2009-3695
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.