Advisory

GHSA-89hj-xfx5-7q66

Also known as: CVE-2014-0473, PYSEC-2014-2

Summary

Django Reuses Cached CSRF Token

Details

The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-05-17 03:07 UTC
Modified
2025-04-13 23:36 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 0, fixed 1.4.11 (ecosystem)

Fixed versions

1.4.11

Fix

  • Fixed version 1.4.11
    pip install --upgrade django==1.4.11

django

PyPI · All systems

Affected

  • introduced 1.5, fixed 1.5.6 (ecosystem)

Fixed versions

1.5.6

Fix

  • Fixed version 1.5.6
    pip install --upgrade django==1.5.6

django

PyPI · All systems

Affected

  • introduced 1.6, fixed 1.6.3 (ecosystem)

Fixed versions

1.6.3

Fix

  • Fixed version 1.6.3
    pip install --upgrade django==1.6.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences