Total vulnerabilities in the database
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.
Software | From | Fixed in |
---|---|---|
djangoproject / django | - | 1.2.6.x |
djangoproject / django | 1.2.5 | 1.2.5.x |
djangoproject / django | 0.95 | 0.95.x |
djangoproject / django | 1.0 | 1.0.x |
djangoproject / django | 1.3 | 1.3.x |
djangoproject / django | 1.1.2 | 1.1.2.x |
djangoproject / django | 1.0.1 | 1.0.1.x |
djangoproject / django | 1.1 | 1.1.x |
djangoproject / django | 1.2.1 | 1.2.1.x |
djangoproject / django | 1.2.4 | 1.2.4.x |
djangoproject / django | 0.91 | 0.91.x |
djangoproject / django | 1.0.2 | 1.0.2.x |
djangoproject / django | 1.2.3 | 1.2.3.x |
djangoproject / django | 1.3-alpha1 | 1.3-alpha1.x |
djangoproject / django | 1.1.3 | 1.1.3.x |
djangoproject / django | 1.2.1-2 | 1.2.1-2.x |
djangoproject / django | 1.2 | 1.2.x |
djangoproject / django | 0.95.1 | 0.95.1.x |
djangoproject / django | 0.96 | 0.96.x |
djangoproject / django | 1.3-alpha2 | 1.3-alpha2.x |
djangoproject / django | 1.1.0 | 1.1.0.x |
djangoproject / django | 1.2.2 | 1.2.2.x |