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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DSA-2332-1 | python-django security update |
![]() |
EUVD-2011-0008 | 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. |
![]() |
GHSA-wxg3-mfph-qg9w | Django Might Allow CSRF Requests via URL Verification |
![]() |
USN-1297-1 | Django vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-07T00:01:51.120Z
Reserved: 2011-10-19T00:00:00
Link: CVE-2011-4138

No data.

Status : Deferred
Published: 2011-10-19T10:55:04.457
Modified: 2025-04-11T00:51:21.963
Link: CVE-2011-4138

No data.

No data.