PyPI: django
CVE-2011-4140
Safety vulnerability ID: SFTY-20111019-91483
Safety legacy ID: pyup.io-33066
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.
Overview
Django Cross-Site Request Forgery vulnerability
Advisory
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.
How to Fix
Mitigation and Workarounds
---
Vulnerable Functions
Functions linked to known vulnerabilities.
References
- https://getsafety.com/vulnerabilities/SFTY-20111019-91483/CVE-2011-4140
- https://nvd.nist.gov/vuln/detail/CVE-2011-4140
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://github.com/advisories/GHSA-h95j-h2rv-qrg4
- https://hermes.opensuse.org/messages/14700881
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://www.debian.org/security/2011/dsa-2332
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-5.yaml
- https://web.archive.org/web/20140806062902/http://secunia.com/advisories/46614
- https://www.djangoproject.com/weblog/2011/sep/09
- https://www.djangoproject.com/weblog/2011/sep/10/127
Verified by Safety
Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.
Learn more