Total vulnerabilities in the database
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
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 |
![]() |
- | 1.2.7 |
![]() |
1.3.0 | 1.3.1 |