Data leakage via cache key collision in Django
An issue was discovered in Django version 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-13254US | medium5.9 | Exploit | ||
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 res… | ||||
02
references
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/3.0/releases/securityWEB
- https://github.com/advisories/GHSA-wpjr-j57x-wxfwADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/07e59caa02831c4569bbebb9eb773bdd9cb4b206WEB
- https://github.com/django/django/commit/84b2da5552e100ae3294f564f6c862fef8d0e693WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2020-31.yamlWEB
- https://groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJWEB
- https://lists.debian.org/debian-lts-announce/2020/06/msg00016.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan