An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system’s standard umask rather than 0o077.
docs.djangoproject.com/en/dev/releases/security/
groups.google.com/forum/#%21topic/django-announce/Gdqn58RqIDM
groups.google.com/forum/#%21topic/django-announce/zFCMdgUnutU
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F2ZHO3GZCJMP3DDTXCNVFV6ED3W64NAU/
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OLGFFLMF3X6USMJD7V5F5P4K2WVUTO3T/
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZCRPQCBTV3RZHKVZ6K6QOAANPRZQD3GI/
security.netapp.com/advisory/ntap-20200918-0004/
usn.ubuntu.com/4479-1/
www.djangoproject.com/weblog/2020/sep/01/security-releases/
www.openwall.com/lists/oss-security/2020/09/01/2
www.oracle.com/security-alerts/cpujan2021.html