CVE-2011-4137

Django vulnerability

CVSS

5.0

EPSS

3.0%

EPSS pct

86th

Exploited

No known

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.

Affected vendor

Djangoproject

Affected product

Django

CVSS vector

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

Weakness type (CWE)

CWE-399

Published

2011-10-19

Risk analysis

Based on its CVSS vector, this vulnerability is exploitable over the network, low attack complexity, requiring no authentication. Successful exploitation leads to partial impact to availability.

Its EPSS score of 3.0% reflects a lower probability of exploitation activity in the wild over the next 30 days, placing it above 86% of all scored CVEs.

Check your external exposure to CVE-2011-4137

Confirm whether Djangoproject Django is running on any internet-facing host or subdomain.
Match discovered service fingerprints against the version affected by CVE-2011-4137.
Prioritise remediation if the asset is public, business-critical, or near authentication/payment flows.

How ThreatPort helps with CVE-2011-4137

ThreatPort's external attack surface scanner checks your internet-facing assets — agentlessly, from the outside in — for the exposed services and versions that CVE-2011-4137 affects, then prioritises the finding by real risk using CISA KEV and FIRST.org EPSS.

Run a free external exposure scan

Are you exposed to CVE-2011-4137?

Run an instant, non-intrusive external scan to check your attack surface for CVE-2011-4137.

Start free scan

No credit card. Agentless.

Related vulnerabilities