CVE-2011-4137
Last modified
CVE-2011-4137 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.02% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | <= 1.2.6 |
| Djangoproject | Django | 0.91 |
| Djangoproject | Django | 0.95 |
| Djangoproject | Django | 0.95.1 |
| Djangoproject | Django | 0.96 |
| Djangoproject | Django | 1.0 |
| Djangoproject | Django | 1.0.1 |
| Djangoproject | Django | 1.0.2 |
| Djangoproject | Django | 1.1 |
| Djangoproject | Django | 1.1.0 |
| Djangoproject | Django | 1.1.2 |
| Djangoproject | Django | 1.1.3 |
| Djangoproject | Django | 1.2 |
| Djangoproject | Django | 1.2.1 |
| Djangoproject | Django | 1.2.2 |
| Djangoproject | Django | 1.2.3 |
| Djangoproject | Django | 1.2.4 |
| Djangoproject | Django | 1.2.5 |
| Djangoproject | Django | 1.3 |
References
- https://www.djangoproject.com/weblog/2011/sep/09/Patch, Vendor Advisory
- https://www.djangoproject.com/weblog/2011/sep/09/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2011-4137?
How severe is CVE-2011-4137?
How do I fix CVE-2011-4137?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2011
- CVE-2011-4131The NFSv4 implementation in the Linux kernel before 3.2.2 do…
- CVE-2011-4132The cleanup_journal_tail function in the Journaling Block De…
- CVE-2011-4133Cross-site request forgery (CSRF) vulnerability in Moodle 1.…
- CVE-2011-4134Heap-based buffer overflow in lmadmin in Flexera FlexNet Pub…
- CVE-2011-4135Multiple directory traversal vulnerabilities in lmgrd in Fle…
- CVE-2011-4136django.contrib.sessions in Django before 1.2.7 and 1.3.x bef…
- CVE-2011-4138The verify_exists functionality in the URLField implementati…
- CVE-2011-4139Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's …
- CVE-2011-4140The CSRF protection mechanism in Django through 1.2.7 and 1.…
- CVE-2011-4141Untrusted search path vulnerability in EMC RSA SecurID Softw…
- CVE-2011-4142The Web Search feature in EMC SourceOne Email Management 6.5…
- CVE-2011-4143EMC RSA enVision 4.0 before SP4 P5 and 4.1 before P3 allows …
Are you affected by CVE-2011-4137?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
