hoch7.5
CVE-2011-4140
Django Cross-Site Request Forgery vulnerability
Auswirkung
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.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Bei Erfolg: hohes Risiko, dass Daten oder Systeme verändert werden.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| pip | Django | <= 1.2.7 | nicht erfasst |
Betroffene Produkte · Djangoproject
| Produkt | Betroffene Versionen |
|---|---|
| Django | bis einschließlich 1.2.6 Versionen 0.91, 0.95, 0.95.1, 0.96, 1.0 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- https://github.com/advisories/GHSA-h95j-h2rv-qrg4
- https://nvd.nist.gov/vuln/detail/CVE-2011-4140
- 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