CVE-2020-13254: Data leakage via cache key collision in Django
(updated )
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.
References
- docs.djangoproject.com/en/3.0/releases/security
- github.com/advisories/GHSA-wpjr-j57x-wxfw
- github.com/django/django
- github.com/django/django/commit/07e59caa02831c4569bbebb9eb773bdd9cb4b206
- github.com/django/django/commit/84b2da5552e100ae3294f564f6c862fef8d0e693
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2020-31.yaml
- groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJ
- lists.debian.org/debian-lts-announce/2020/06/msg00016.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ
- nvd.nist.gov/vuln/detail/CVE-2020-13254
- security.netapp.com/advisory/ntap-20200611-0002
- usn.ubuntu.com/4381-1
- usn.ubuntu.com/4381-2
- www.debian.org/security/2020/dsa-4705
- www.djangoproject.com/weblog/2020/jun/03/security-releases
- www.oracle.com/security-alerts/cpujan2021.html
Code Behaviors & Features
Detect and mitigate CVE-2020-13254 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →