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.
The product does not validate, or incorrectly validates, a certificate.
Link | Tags |
---|---|
https://usn.ubuntu.com/4381-1/ | third party advisory vendor advisory |
https://usn.ubuntu.com/4381-2/ | third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2020/06/msg00016.html | third party advisory mailing list |
https://www.debian.org/security/2020/dsa-4705 | third party advisory vendor advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/ | vendor advisory |
https://www.oracle.com/security-alerts/cpujan2021.html | third party advisory patch |
https://docs.djangoproject.com/en/3.0/releases/security/ | release notes vendor advisory |
https://groups.google.com/d/msg/django-announce/pPEmb2ot4Fo/X-SMalYSBAAJ | mailing list third party advisory release notes |
https://www.djangoproject.com/weblog/2020/jun/03/security-releases/ | release notes vendor advisory |
https://security.netapp.com/advisory/ntap-20200611-0002/ | third party advisory |