CVE-2011-4137

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.

Severity
not scored
CVSS v3
not scored
Exploit chance (EPSS)
3.024%
chance of exploitation in the next 30 days
higher than 87.7% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2011-10-19Published by the CNA10:00 UTC
  2. 2018-07-23GitHub advisory published (GHSA-3jqw-crqj-w8qw)2469 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-3jqw-crqj-w8qw, affected packages:

EcosystemPackageVulnerable rangePatched
PyPIdjango< 1.2.71.2.7
PyPIdjango>= 1.3, < 1.3.11.3.1

Affected products

VendorProduct
djangoprojectdjango

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources