Django security releases issued: 3.1.8, 3.0.14, and 2.2.20
In accordance with our security release policy, the Django team is issuing Django 3.1.8, Django 3.0.14 and Django 2.2.20. These releases address the security issue with severity "low" detailed below. We encourage all users of Django to upgrade as soon as possible.
CVE-2021-28658: Potential directory-traversal via uploaded files
MultiPartParser allowed directory-traversal via uploaded files with suitably crafted file names.
Built-in upload handlers were not affected by this vulnerability.
Thank you to Dennis Brinkrolf for the report.
Affected supported versions
- Django main branch
- Django 3.2 (which will be released in a separate blog post later today)
- Django 3.1
- Django 3.0
- Django 2.2
Resolution
Patches to resolve the issue have been applied to Django's main branch and the 3.2, 3.1, 3.0, and 2.2 release branches. The patches may be obtained from the following changesets:
- On the main branch
- On the 3.2 release branch
- On the 3.1 release branch
- On the 3.0 release branch
- On the 2.2 release branch
The following releases have been issued:
- Django 3.1.8 (download Django 3.1.8 | 3.1.8 checksums)
- Django 3.0.14 (download Django 3.0.14 | 3.0.14 checksums)
- Django 2.2.20 (download Django 2.2.20 | 2.2.20 checksums)
The PGP key ID used for this release is Mariusz Felisiak: 2EF56372BA48CD1B.
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email to security@djangoproject.com, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.
