CVE-2011-4138
Description
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 1.3.1-1 |
| sid | Fixed | 1.3.1-1 |
| forky | Fixed | 1.3.1-1 |
| bullseye | Fixed | 1.3.1-1 |
| bookworm | Fixed | 1.3.1-1 |
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| djangoproject | django | {"endIncluding":"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
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- https://nvd.nist.gov/vuln/detail/CVE-2011-4138
- https://github.com/django/django/commit/1a76dbefdfc60e2d5954c0ba614c3d054ba9c3f0
- https://github.com/django/django/commit/7268f8af86186518821d775c530d5558fd726930
- https://github.com/django/django
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-3.yaml
- https://www.djangoproject.com/weblog/2011/sep/09
- https://www.djangoproject.com/weblog/2011/sep/10/127
- https://security-tracker.debian.org/tracker/CVE-2011-4138
CWEs
CWE-20
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.