CVE-2011-4140: CSRF
First published: Wed Oct 19 2011(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/Django | >=1.3<=1.3.1 | |
| pip/Django | <=1.2.7 | |
| Django | <=1.2.6 | |
| Django | =0.91 | |
| Django | =0.95 | |
| Django | =0.95.1 | |
| Django | =0.96 | |
| Django | =1.0 | |
| Django | =1.0.1 | |
| Django | =1.0.2 | |
| Django | =1.1 | |
| Django | =1.1.0 | |
| Django | =1.1.2 | |
| Django | =1.1.3 | |
| Django | =1.2 | |
| Django | =1.2.1 | |
| Django | =1.2.1-2 | |
| Django | =1.2.2 | |
| Django | =1.2.3 | |
| Django | =1.2.4 | |
| Django | =1.2.5 | |
| Django | =1.3 | |
| Django | =1.3-alpha1 | |
| Django | =1.3-alpha2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- http://openwall.com/lists/oss-security/2011/09/11/1
- https://www.djangoproject.com/weblog/2011/sep/09/
- http://openwall.com/lists/oss-security/2011/09/13/2
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
- https://hermes.opensuse.org/messages/14700881
- https://nvd.nist.gov/vuln/detail/CVE-2011-4140
- https://github.com/advisories/GHSA-h95j-h2rv-qrg4 (Advisory)
- 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
Frequently Asked Questions
What is the severity of CVE-2011-4140?
CVE-2011-4140 is classified as a medium severity vulnerability.
How do I fix CVE-2011-4140?
To fix CVE-2011-4140, upgrade Django to version 1.3.2 or later.
What versions of Django are affected by CVE-2011-4140?
CVE-2011-4140 affects Django versions from 0.91 to 1.3.1, including several intermediate versions.
Can CVE-2011-4140 lead to unauthorized access?
Yes, CVE-2011-4140 can allow attackers to make unauthenticated forged requests, potentially leading to unauthorized access.
Is there a workaround for CVE-2011-4140 if I cannot upgrade?
A potential workaround includes configuring your web server to sanitize HTTP Host headers, although upgrading is strongly recommended.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/weakness
- agent/description
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-h95j-h2rv-qrg4
- alias/CVE-2011-4140
- agent/software-canonical-lookup
- agent/references
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/author
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-historical
- collector/nvd-index
- package-manager/pip
- vendor/djangoproject
- canonical/django
- version/django/1.2.6
- version/django/0.91
- version/django/0.95
- version/django/0.95.1
- version/django/0.96
- version/django/1.0
- version/django/1.0.1
- version/django/1.0.2
- version/django/1.1
- version/django/1.1.0
- version/django/1.1.2
- version/django/1.1.3
- version/django/1.2
- version/django/1.2.1
- version/django/1.2.1-2
- version/django/1.2.2
- version/django/1.2.3
- version/django/1.2.4
- version/django/1.2.5
- version/django/1.3
- version/django/1.3-alpha1
- version/django/1.3-alpha2