p PatchFirst

CVE-2011-4140

CVE-2011-4140

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.5 · High · EPSS 1.1% · Fix available

Published
Updated

Stack: system · python

Affected products and versions

  • n/a

    Versions
    • n/a: Affected

    No fix published

  • python-django Debian:12

    Affected ranges
    • ECOSYSTEM: < 1.3.1-1

    Update to 1.3.1-1

  • python-django Debian:13

    Affected ranges
    • ECOSYSTEM: < 1.3.1-1

    Update to 1.3.1-1

  • python-django Debian:14

    Affected ranges
    • ECOSYSTEM: < 1.3.1-1

    Update to 1.3.1-1

  • django PyPI

    Versions
    • 1.0.1
    • 1.0.2
    • 1.0.3
    • 1.0.4
    • 1.1
    • 1.1.1
    • 1.1.2
    • 1.1.3
    • 1.1.4
    • 1.2
    • 1.2.1
    • 1.2.2
    • 1.2.3
    • 1.2.4
    • 1.2.5
    • 1.2.6
    • 1.2.7
    Affected ranges
    • ECOSYSTEM: ≤ 1.2.7

    No fix published

  • django PyPI

    Versions
    • 1.3
    • 1.3.1
    Affected ranges
    • ECOSYSTEM: ≥ 1.3, ≤ 1.3.1

    No fix published

  • django PyPI

    Versions
    • 1.0.1
    • 1.0.2
    • 1.0.3
    • 1.0.4
    • 1.1
    • 1.1.1
    • 1.1.2
    • 1.1.3
    • 1.1.4
    • 1.2
    • 1.2.1
    • 1.2.2
    • 1.2.3
    • 1.2.4
    • 1.2.5
    • 1.2.6
    • 1.3
    Affected ranges
    • ECOSYSTEM: < 1.2.7 ∪ ≥ 1.3, < 1.3.1

    Update to 1.2.7; Update to 1.3.1

Original sources

Check your server →