CVE-2009-3695
First published: Tue Oct 13 2009(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Djangoproject Django | =1.0 | |
| Djangoproject Django | =1.1 | |
| pip/Django | >=1.1.0<1.1.1 | 1.1.1 |
| pip/Django | >=1.0.0<1.0.4 | 1.0.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/36655
- http://groups.google.com/group/django-users/browse_thread/thread/15df9e45118dfc51/
- http://secunia.com/advisories/36948
- http://www.debian.org/security/2009/dsa-1905
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550457
- http://www.vupen.com/english/advisories/2009/2871
- http://www.djangoproject.com/weblog/2009/oct/09/security/
- http://secunia.com/advisories/36968
- http://www.openwall.com/lists/oss-security/2009/10/13/6
- https://exchange.xforce.ibmcloud.com/vulnerabilities/53727
- https://nvd.nist.gov/vuln/detail/CVE-2009-3695
- https://web.archive.org/web/20200228171918/http://www.securityfocus.com/bid/36655
- https://github.com/django/django/commit/594a28a9044120bed58671dde8a805c9e0f6c79a
- https://github.com/django/django/commit/e3e992e18b368fcd56aabafc1b5bf80a6e11b495
- http://groups.google.com/group/django-users/browse_thread/thread/15df9e45118dfc51
- http://www.djangoproject.com/weblog/2009/oct/09/security
- https://github.com/advisories/GHSA-p6m5-h7pp-v2x5 (Advisory)
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2009-4.yaml
- https://web.archive.org/web/20091013093057/http://secunia.com/advisories/36968
- https://web.archive.org/web/20091017070244/http://secunia.com/advisories/36948
Frequently Asked Questions
What is the severity of CVE-2009-3695?
CVE-2009-3695 is classified as a high-severity vulnerability due to its potential to cause a denial of service through CPU consumption.
How do I fix CVE-2009-3695?
To fix CVE-2009-3695, upgrade Django to version 1.0.4 or 1.1.1 or later.
Which versions of Django are affected by CVE-2009-3695?
CVE-2009-3695 affects Django versions 1.0 before 1.0.4 and 1.1 before 1.1.1.
What type of attack can exploit CVE-2009-3695?
CVE-2009-3695 can be exploited through crafted EmailField or URLField inputs that trigger excessive backtracking in regular expressions.
What impact does CVE-2009-3695 have on web applications?
CVE-2009-3695 can lead to denial of service by exhausting server CPU resources, potentially making the web application unresponsive.
- collector/nvd-historical
- collector/nvd-index
- agent/type
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/author
- agent/remedy
- agent/description
- agent/weakness
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- agent/event
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-p6m5-h7pp-v2x5
- alias/CVE-2009-3695
- agent/references
- agent/severity
- agent/last-modified-date
- collector/github-advisory
- agent/trending
- agent/tags
- agent/source
- vendor/djangoproject
- canonical/djangoproject django
- version/djangoproject django/1.0
- version/djangoproject django/1.1
- package-manager/pip