CVE-2009-3695 Django Regex Algorithmic Complexity Causes Denial of Service

Medium 5.0 Published Updated

Remote attackers can cause denial of service via CPU exhaustion using crafted email or URL inputs in Django forms.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2009-3695?

CVE-2009-3695 is a medium-severity denial of service vulnerability in Djangoproject Django, published on 13 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Which versions are affected by CVE-2009-3695?

5 open source packages ship an affected version, including django and Django. It affects 1 product.

PackageAffectedFixed in
django PyPIFrom 1.01.0.4, 1.1.1
django PyPIFrom 1.01.0.4
django PyPIFrom 1.11.1.1
Django PyPIFrom 1.01.0.4
Django PyPIFrom 1.11.1.1

Products include Djangoproject Django.

How do I fix CVE-2009-3695?

Upgrade django to a fixed version for your release line: 1.0.4 or 1.1.1.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2009-3695 being exploited?

There is no known exploitation of CVE-2009-3695 in the wild and no public exploit code.

All Djangoproject Django vulnerabilities

Sources

Also known as CVE-2009-3610, DEBIAN-CVE-2009-3695, DSA-1905-1, GHSA-p6m5-h7pp-v2x5, PYSEC-2009-4.

Is CVE-2009-3695 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free