Skip to content
Fencer Intel
high 7.5

CVE-2011-4137 json

Denial of service in django

published 2011-10-19 15 y ago modified 2026-06-16 4 mo ago also GHSA-3jqw-crqj-w8qw , PYSEC-2011-2 , EUVD-2011-0007

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
3.0%
EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 1.2.7, 1.3.1
  • python-django Debian 14, Debian 13, Debian 12 1.3.1-1

debian advisories DEBIAN-CVE-2011-4137

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4137 updated cvss 4.3

Django: v1.3.1, v1.2.7 multiple security flaws

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.02% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi django
<1.2.7
>=1.3, <1.3.1
1.2.7
1.3.1

Classification

Weakness
  • CWE-399 Resource Management Errors
  • CWE-1088 Synchronous Access of Remote Resource without Timeout
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.