First published: Tue Jan 04 2022(Updated: )
Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are directly passed to it.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=2.2<2.2.26 | |
Djangoproject Django | >=3.2<3.2.11 | |
Djangoproject Django | >=4.0<4.0.1 | |
Fedoraproject Fedora | =35 | |
redhat/Django | <4.0.1 | 4.0.1 |
redhat/Django | <3.2.11 | 3.2.11 |
redhat/Django | <2.2.26 | 2.2.26 |
pip/Django | >=4.0<4.0.1 | 4.0.1 |
pip/Django | >=3.2<3.2.11 | 3.2.11 |
pip/Django | >=2.2<2.2.26 | 2.2.26 |
>=2.2<2.2.26 | ||
>=3.2<3.2.11 | ||
>=4.0<4.0.1 | ||
=35 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-45452 is a vulnerability in Django versions 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 that allows directory traversal if crafted filenames are directly passed to the Storage.save function.
The severity of CVE-2021-45452 is medium with a CVSS score of 5.3.
You can check if your Django version is affected by CVE-2021-45452 by comparing the version number with the affected versions: 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1.
To fix CVE-2021-45452 in Django, you need to update to version 2.2.26, 3.2.11, or 4.0.1, depending on the version you are using.
Yes, you can find references for CVE-2021-45452 at the following links: [Reference 1](https://www.djangoproject.com/weblog/2022/jan/04/security-releases/), [Reference 2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2037170), [Reference 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2037171).