An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. In cases where a memcached backend does not perform key validation, passing malformed cache keys could result in a key collision, and potential data leakage.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2233-1 | python-django security update |
Debian DLA |
DLA-2233-2 | python-django regression update |
Debian DSA |
DSA-4705-1 | python-django security update |
Github GHSA |
GHSA-wpjr-j57x-wxfw | Data leakage via cache key collision in Django |
Ubuntu USN |
USN-4381-1 | Django vulnerabilities |
Ubuntu USN |
USN-4381-2 | Django vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T12:11:19.484Z
Reserved: 2020-05-21T00:00:00
Link: CVE-2020-13254
No data.
Status : Modified
Published: 2020-06-03T14:15:12.563
Modified: 2024-11-21T05:00:53.270
Link: CVE-2020-13254
OpenCVE Enrichment
No data.
Debian DLA
Debian DSA
Github GHSA
Ubuntu USN