CVE-2011-4137

CVE-2011-4137 is a medium-severity vulnerability in Djangoproject Django with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-399.

Key facts

• Severity: Medium (CVSS 2.0 base score 5.0)
• EPSS exploit prediction: 3% (86th percentile)
• Actively exploited: Not listed in CISA KEV
• Weakness: CWE-399
• Affected product: Djangoproject Django
• Published: 2011-10-19
• Last modified: 2026-06-16

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.

Frequently asked questions

What is CVE-2011-4137?

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.

How severe is CVE-2011-4137?

CVE-2011-4137 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2011-4137 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (86th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2011-4137?

CVE-2011-4137 primarily affects Djangoproject Django. In total, 22 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2011-4137?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2011-4137 published?

CVE-2011-4137 was published on 2011-10-19 and last updated on 2026-06-16.

References

• http://openwall.com/lists/oss-security/2011/09/11/1
• http://openwall.com/lists/oss-security/2011/09/13/2
• http://openwall.com/lists/oss-security/2011/09/15/5
• http://secunia.com/advisories/46614
• http://www.debian.org/security/2011/dsa-2332
• https://bugzilla.redhat.com/show_bug.cgi?id=737366
• https://hermes.opensuse.org/messages/14700881
• https://www.djangoproject.com/weblog/2011/sep/09/
• https://www.djangoproject.com/weblog/2011/sep/10/127/

Affected products (22)

• cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:0.91:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:0.95:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:0.95.1:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:0.96:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.0:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.0.1:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.0.2:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.1:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.1.0:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.1.2:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.1.3:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.1:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.1:2:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.2:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.3:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.4:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.2.5:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.3:*:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.3:alpha1:*:*:*:*:*:*
• cpe:2.3:a:djangoproject:django:1.3:alpha2:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

• CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
• CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
• CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
• CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
• CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
• CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-399 (Resource Management Errors) vulnerabilities

• CVE-2015-8104 — Critical (CVSS 10.0): The KVM subsystem in the Linux kernel through 4.2.6, and Xen 4.3.x through 4.6.x, allows guest OS users to cause a…
• CVE-2015-0339 — Critical (CVSS 10.0): Adobe Flash Player before 13.0.0.277 and 14.x through 17.x before 17.0.0.134 on Windows and OS X and before…
• CVE-2015-0335 — Critical (CVSS 10.0): Adobe Flash Player before 13.0.0.277 and 14.x through 17.x before 17.0.0.134 on Windows and OS X and before…
• CVE-2015-0333 — Critical (CVSS 10.0): Adobe Flash Player before 13.0.0.277 and 14.x through 17.x before 17.0.0.134 on Windows and OS X and before…
• CVE-2014-4121 — Critical (CVSS 10.0): Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2 does not properly parse internationalized…
• CVE-2014-0560 — Critical (CVSS 10.0): Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.12 and 11.x before 11.0.09 on Windows and OS…

Browse all CWE-399 (Resource Management Errors) vulnerabilities →