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.
Weakness
The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Django |
Djangoproject |
0.91 |
0.91 |
| Django |
Djangoproject |
0.95 |
0.95 |
| Django |
Djangoproject |
0.95.1 |
0.95.1 |
| Django |
Djangoproject |
0.96 |
0.96 |
| Django |
Djangoproject |
1.0 |
1.0 |
| Django |
Djangoproject |
1.0.1 |
1.0.1 |
| Django |
Djangoproject |
1.0.2 |
1.0.2 |
| Django |
Djangoproject |
1.1 |
1.1 |
| Django |
Djangoproject |
1.1.0 |
1.1.0 |
| Django |
Djangoproject |
1.1.2 |
1.1.2 |
| Django |
Djangoproject |
1.1.3 |
1.1.3 |
| Django |
Djangoproject |
1.2 |
1.2 |
| Django |
Djangoproject |
1.2.1 |
1.2.1 |
| Django |
Djangoproject |
1.2.1 |
1.2.1 |
| Django |
Djangoproject |
1.2.2 |
1.2.2 |
| Django |
Djangoproject |
1.2.3 |
1.2.3 |
| Django |
Djangoproject |
1.2.4 |
1.2.4 |
| Django |
Djangoproject |
1.2.5 |
1.2.5 |
| Django |
Djangoproject |
* |
1.2.6 |
| Django |
Djangoproject |
1.3 |
1.3 |
| Django |
Djangoproject |
1.3 |
1.3 |
| Django |
Djangoproject |
1.3 |
1.3 |
Potential Mitigations
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Use the “double-submitted cookie” method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
References