CVE-2009-3695: High severity 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 Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
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.