Django: cached data possibly served to the wrong session
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-2934-1 | python-django security update |
EUVD |
EUVD-2014-0008 | Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers. |
Github GHSA |
GHSA-q7q2-qf2q-rw3w | Django Vulnerable to Cache Poisoning |
Ubuntu USN |
USN-2212-1 | Django vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.6% (2.617% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.