—

PYSEC-2011-5

Details

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

PyPI / django

Introduced in: 0 Fixed in: 1.2.7

Fix pip install --upgrade 'django>=1.2.7'

References

https://bugzilla.redhat.com/show_bug.cgi?id=737366 [REPORT]
http://openwall.com/lists/oss-security/2011/09/11/1 [WEB]
https://www.djangoproject.com/weblog/2011/sep/09/ [ARTICLE]
http://openwall.com/lists/oss-security/2011/09/13/2 [WEB]
https://www.djangoproject.com/weblog/2011/sep/10/127/ [ARTICLE]
http://secunia.com/advisories/46614 [ADVISORY]
http://www.debian.org/security/2011/dsa-2332 [ADVISORY]
https://hermes.opensuse.org/messages/14700881 [WEB]
https://github.com/advisories/GHSA-h95j-h2rv-qrg4 [ADVISORY]