CVE-2011-4140
Last modified
CVE-2011-4140 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.09% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Djangoproject | Django | <= 1.2.6 |
| Djangoproject | Django | 0.91 |
| Djangoproject | Django | 0.95 |
| Djangoproject | Django | 0.95.1 |
| Djangoproject | Django | 0.96 |
| Djangoproject | Django | 1.0 |
| Djangoproject | Django | 1.0.1 |
| Djangoproject | Django | 1.0.2 |
| Djangoproject | Django | 1.1 |
| Djangoproject | Django | 1.1.0 |
| Djangoproject | Django | 1.1.2 |
| Djangoproject | Django | 1.1.3 |
| Djangoproject | Django | 1.2 |
| Djangoproject | Django | 1.2.1 |
| Djangoproject | Django | 1.2.2 |
| Djangoproject | Django | 1.2.3 |
| Djangoproject | Django | 1.2.4 |
| Djangoproject | Django | 1.2.5 |
| Djangoproject | Django | 1.3 |
References
- https://www.djangoproject.com/weblog/2011/sep/09/Patch, Vendor Advisory
- https://www.djangoproject.com/weblog/2011/sep/09/Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2011-4140?
How severe is CVE-2011-4140?
How do I fix CVE-2011-4140?
Are you affected by CVE-2011-4140?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
