CVE-2009-3695

UnknownEPSS 3.69%

Last modified

CVE-2009-3695 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.69% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
3.69%

88.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
DjangoprojectDjango1.0
DjangoprojectDjango1.1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2009-3695?
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.
How severe is CVE-2009-3695?
Severity scoring for CVE-2009-3695 is pending analysis. The EPSS model estimates a 3.69% probability of exploitation in the next 30 days.
How do I fix CVE-2009-3695?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2009-3695?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST