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.
https://www.djangoproject.com/weblog/2011/sep/10/127/
https://www.djangoproject.com/weblog/2011/sep/09/
https://hermes.opensuse.org/messages/14700881
https://bugzilla.redhat.com/show_bug.cgi?id=737366
http://www.debian.org/security/2011/dsa-2332
http://secunia.com/advisories/46614