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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://hermes.opensuse.org/messages/14700881 | vendor advisory |
http://www.debian.org/security/2011/dsa-2332 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=737366 | patch |
http://secunia.com/advisories/46614 | third party advisory |
http://openwall.com/lists/oss-security/2011/09/11/1 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/10/127/ | patch |
http://openwall.com/lists/oss-security/2011/09/13/2 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/09/ | patch vendor advisory |