Quick answers
- Is CVE-2011-4137 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2011-4137 being exploited in the wild.
- How severe is CVE-2011-4137?
- Low severity, with a CVSS score of 3.1, published 19 October 2011.
- Which products and versions are affected?
- Django (PyPI) ECOSYSTEM:introduced=0,fixed=1.2.7, ECOSYSTEM:introduced=0,fixed=1.2.7,introduced=1.3,fixed=1.3.1.
- Is there a fix for CVE-2011-4137?
- Yes. Django (PyPI): upgrade to 1.2.7, 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2011-4137 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2011-4137?
- Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Django (PyPI): upgrade to 1.2.7, 1.3.1 or later
pip install "Django>=1.3.1"
Technical details
The vulnerability exists in Django's URLField validator verify_exists functionality, which attempted to verify URLs by making HTTP requests using Python's urllib2 library without imposing timeout constraints. An attacker can exploit this by submitting specially crafted URLs that respond very slowly, maintain open connections without sending data, or return extremely large responses, causing the Django process to consume resources and become unresponsive. The vulnerability affects Django versions before 1.2.7 and 1.3.x before 1.3.1. The fix removes the verify_exists functionality entirely, replacing it with safer URL validation that does not make network requests.
Affected products
- Django Django before 1.2.7 and 1.3.x before 1.3.1
Identifiers
- CVE-2011-4137
- GHSA-3jqw-crqj-w8qw
- PYSEC-2011-2
Timeline
- 2011-09-09: disclosed
- 2011-09-10: patched
- 2018-07-23: advisory