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.
2011-10-19T10:55:04.643
2025-04-11T00:51:21.963
Deferred
CVSSv2: 6.8 (MEDIUM)
AV:N/AC:M/Au:N/C:P/I:P/A:P
8.6
6.4
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | djangoproject | django | ≤ 1.2.6 | Yes |
Application | djangoproject | django | 0.91 | Yes |
Application | djangoproject | django | 0.95 | Yes |
Application | djangoproject | django | 0.95.1 | Yes |
Application | djangoproject | django | 0.96 | Yes |
Application | djangoproject | django | 1.0 | Yes |
Application | djangoproject | django | 1.0.1 | Yes |
Application | djangoproject | django | 1.0.2 | Yes |
Application | djangoproject | django | 1.1 | Yes |
Application | djangoproject | django | 1.1.0 | Yes |
Application | djangoproject | django | 1.1.2 | Yes |
Application | djangoproject | django | 1.1.3 | Yes |
Application | djangoproject | django | 1.2 | Yes |
Application | djangoproject | django | 1.2.1 | Yes |
Application | djangoproject | django | 1.2.1 | Yes |
Application | djangoproject | django | 1.2.2 | Yes |
Application | djangoproject | django | 1.2.3 | Yes |
Application | djangoproject | django | 1.2.4 | Yes |
Application | djangoproject | django | 1.2.5 | Yes |
Application | djangoproject | django | 1.3 | Yes |
Application | djangoproject | django | 1.3 | Yes |
Application | djangoproject | django | 1.3 | Yes |