CVE-2011-4137 Denial of service in django

What is CVE-2011-4137?

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

Official description

The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.

Weakness: CWE-399

Which versions are affected by CVE-2011-4137?

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

Products include Djangoproject Django.

How do I fix CVE-2011-4137?

Upgrade django to a fixed version for your release line: 1.2.7 or 1.3.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-2011-4137 being exploited?

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

Other vulnerabilities in Djangoproject Django

• CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin Critical 9.8
• CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle Critical 9.8
• CVE-2024-42005 Django SQL injection vulnerability Critical 9.8
• CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files Critical 9.8
• CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection Critical 9.8

All Djangoproject Django vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as DEBIAN-CVE-2011-4137, GHSA-3jqw-crqj-w8qw, PYSEC-2011-2.