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.
docs.djangoproject.com/en/3.0/releases/security/
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%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/
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