CVE-2011-4137 — MEDIUM (5.0)

Q: How severe is CVE-2011-4137?

CVE-2011-4137 has been rated MEDIUM with a CVSS base score of 5.0/10. Review the CVSS metrics above for detailed severity breakdown.

Q: Is there a patch for CVE-2011-4137?

Check the references section above for vendor advisories and patch information. Affected products include: Djangoproject Django.

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.

CVSS Score

5.0

MEDIUM

AV:N/AC:L/Au:N/C:N/I:N/A:P

Confidentiality

NONE

Integrity

NONE

Availability

PARTIAL

Affected Products

Vendor	Product	Versions
Djangoproject	Django	<= 1.2.6

Related Weaknesses (CWE)

CWE-399

References

FAQ

What is CVE-2011-4137?

CVE-2011-4137 is a vulnerability with a CVSS score of 5.0 (MEDIUM). 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 a...

How severe is CVE-2011-4137?

CVE-2011-4137 has been rated MEDIUM with a CVSS base score of 5.0/10. Review the CVSS metrics above for detailed severity breakdown.

Is there a patch for CVE-2011-4137?

Check the references section above for vendor advisories and patch information. Affected products include: Djangoproject Django.