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.
Published: 2011-10-19
Score: 6.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-2332-1 python-django security update
EUVD EUVD EUVD-2011-0010 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.
Github GHSA Github GHSA GHSA-h95j-h2rv-qrg4 Django Cross-Site Request Forgery vulnerability
History

No history.

Subscriptions

Djangoproject Django
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-07T00:01:51.120Z

Reserved: 2011-10-19T00:00:00.000Z

Link: CVE-2011-4140

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2011-10-19T10:55:04.643

Modified: 2025-04-11T00:51:21.963

Link: CVE-2011-4140

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses