CVE-2011-4138
N/A
Published: October 19, 2011 at 10:00 AM UTC
Updated: June 16, 2026 at 11:34 PM UTC
1 product affected across 1 vendorDjango
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
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.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (8)
Mailing Listx_refsource_MLISTPatch
Source: [email protected]
http://openwall.com/lists/oss-security/2011/09/11/1Mailing Listx_refsource_MLISTPatch
Source: [email protected]
http://openwall.com/lists/oss-security/2011/09/13/2Vendor Advisoryx_refsource_DEBIAN
Source: [email protected]
http://www.debian.org/security/2011/dsa-2332Vendor Advisoryx_refsource_SUSE
Source: [email protected]
https://hermes.opensuse.org/messages/14700881x_refsource_CONFIRMPatchVendor Advisory
Source: [email protected]
https://www.djangoproject.com/weblog/2011/sep/09/x_refsource_CONFIRMPatch
Source: [email protected]
https://www.djangoproject.com/weblog/2011/sep/10/127/Quick Info
StatusMODIFIED
CWE
CWE-20
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card