CVE-2011-4137: High severity django vulnerability
The verifyexists 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 Software
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2011-4137?
CVE-2011-4137 is classified as a medium severity vulnerability due to potential denial of service impacts.
How do I fix CVE-2011-4137?
To mitigate CVE-2011-4137, upgrade Django to version 1.3.1 or later, or version 1.2.7.
What is the impact of CVE-2011-4137?
CVE-2011-4137 allows remote attackers to consume server resources, leading to denial of service.
Which versions of Django are affected by CVE-2011-4137?
Versions of Django before 1.2.7 and 1.3.x before 1.3.1 are affected by CVE-2011-4137.
What functionalities does CVE-2011-4137 exploit?
CVE-2011-4137 exploits the verify_exists functionality in the URLField implementation.