CVE-2011-4140
Medium
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.
SeverityMedium
CVSS6.8
Exploit probability—
Product
Django
PublishedOct 19, 2011
First seenOct 19, 2011
How to fix
Update
- django1.2.7, 1.3.1 or later
Vendor advisories
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| djangoproject django | v ≤ 1.2.6, 0.91, 0.95, 0.95.1, 0.96, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.0, 1.1.2, 1.1.3, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3 | — |
| djangoPyPI | v ≤ 1.2.7, 1.3 ≤ v ≤ 1.3.1, v < 1.2.7, 1.3 ≤ v < 1.3.1 | 1.2.7, 1.3.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.