Vulnerabilities · 2011 · Djangoproject
CVE-2011-4137
Djangoproject Django vulnerability
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.
Affected products
Django. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.djangoproject.com/weblog/2011/sep/09/ · Patch
- openwall.com/lists/oss-security/2011/09/11/1 · Patch
- openwall.com/lists/oss-security/2011/09/13/2 · Patch
- bugzilla.redhat.com/show_bug.cgi?id=737366 · Patch
- www.djangoproject.com/weblog/2011/sep/10/127/ · Patch
- openwall.com/lists/oss-security/2011/09/15/5
- secunia.com/advisories/46614
- www.debian.org/security/2011/dsa-2332
- nvd.nist.gov/vuln/detail/CVE-2011-4137
- cve.org/CVERecord?id=CVE-2011-4137
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.