Django security releases issued: 4.0.7 and 3.2.15
In accordance with our security release policy, the Django team is issuing Django 4.0.7, and Django 3.2.15. These releases addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
CVE-2022-36359: Potential reflected file download vulnerability in FileResponse
An application may have been vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename was derived from user-supplied input. The filename is now escaped to avoid this possibility.
This issue has high severity, according to the Django security policy.
Thanks to Motoyasu Saburi for the report.
Affected supported versions
- Django main branch
- Django 4.1 (which will be released in a separate blog post later today)
- Django 4.0
- Django 3.2
Patches to resolve the issue have been applied to Django's main branch and the 4.1, 4.0, and 3.2 release branches. The patches may be obtained from the following changesets:
The following releases have been issued:
- Django 4.0.7 (download Django 4.0.7 | 4.0.7 checksums)
- Django 3.2.15 (download Django 3.2.15 | 3.2.15 checksums)
The PGP key ID used for this release is Carlton Gibson: E17DF5C82B4F9D00.
General notes regarding security reporting
As always, we ask that potential security issues be reported via private email to email@example.com, and not via Django's Trac instance or the django-developers list. Please see our security policies for further information.