The CSRF protection mechanism in Django up to and including 1.2.7 and 1.3.x up to and including 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote malicious users to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
djangoproject django 0.95 |
||
djangoproject django 0.95.1 |
||
djangoproject django 1.2.3 |
||
djangoproject django 1.1.0 |
||
djangoproject django 1.1.3 |
||
djangoproject django 1.2.4 |
||
djangoproject django 1.2.5 |
||
djangoproject django 1.1 |
||
djangoproject django 1.0 |
||
djangoproject django 1.3 |
||
djangoproject django 1.2 |
||
djangoproject django 1.2.1 |
||
djangoproject django 1.1.2 |
||
djangoproject django 1.0.2 |
||
djangoproject django |
||
djangoproject django 0.91 |
||
djangoproject django 1.2.2 |
||
djangoproject django 1.0.1 |
||
djangoproject django 0.96 |
Vulmon