CVE-2011-4140 in Django
Riassunto
di MITRE
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.