CVE-2011-4137 - CVE House
Back to Database
Status published Medium CVE-2011-4137

The verify_exists functionality in the URLField implementation in Django before...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2011-4137

Credits & Attribution

No credits recorded in the NVD database.

References

More from djangoproject

View All →
CVE-2025-64460
Potential denial-of-service vulnerability in XML serializer text extraction
Unknown 0
CVE-2025-64459
Potential SQL injection via _connector keyword argument in QuerySet and Q objects
Unknown 0
CVE-2025-64458
Potential denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
Unknown 0
CVE-2025-59682
An issue was discovered in Django 4.2 before 4.2.25, 5.1...
Low 3.1
CVE-2025-59681
An issue was discovered in Django 4.2 before 4.2.25, 5.1...
High 7.1

Affected Vendor

djangoproject

View all reports →

Affected Software

django
Vulnerable Versions:
0, 0.91, 0.95, 0.95.1, 0.96, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.0, 1.1.2, 1.1.3, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3

Timeline

Official Publish: October 19th, 2011
Last Modified: August 7th, 2024
Added to House: July 19th, 2026

CVSS Vectors

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.