First published: Tue Sep 01 2020(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=2.2<2.2.16 | |
Djangoproject Django | >=3.0<3.0.10 | |
Djangoproject Django | >=3.1<3.1.1 | |
Canonical Ubuntu Linux | =20.04 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
Fedoraproject Fedora | =33 | |
Oracle ZFS Storage Appliance Kit | =8.8 | |
pip/django | >=3.1<3.1.1 | 3.1.1 |
pip/django | >=3.0<3.0.10 | 3.0.10 |
pip/django | >=2.2<2.2.16 | 2.2.16 |
debian/python-django | 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:4.2.16-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-24584 is a vulnerability discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1.
CVE-2020-24584 has a severity rating of 7.5, which is considered high.
CVE-2020-24584 affects Django versions 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1.
The remedy for CVE-2020-24584 is to upgrade Django to version 3.1.1, 3.0.10, or 2.2.16 depending on the version you are using.
You can find more information about CVE-2020-24584 in the following references: [NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-24584), [GitHub](https://github.com/django/django/commit/1853724acaf17ed7414d54c7d2b5563a25025a71), [Django Releases](https://docs.djangoproject.com/en/dev/releases/security/)