====================================================================

                             CERT-Renater

                 Note d'Information No. 2021/VULN303
_____________________________________________________________________

DATE                : 02/06/2021

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Django versions prior to 3.2.4,
                                     3.1.12, 2.2.24.

=====================================================================
https://www.djangoproject.com/weblog/2021/jun/02/security-releases/
_____________________________________________________________________

Django security releases issued: 3.2.4, 3.1.12, and 2.2.24
Posted by Carlton Gibson on juin 2, 2021


In accordance with our security release policy, the Django team is
issuing Django 3.2.4, Django 3.1.12, and Django 2.2.24. These release
addresses the security issue detailed below. We encourage all users of
Django to upgrade as soon as possible.

CVE-2021-33203: Potential directory traversal via admindocs
Staff members could use the admindocs TemplateDetailView view to check
the existence of arbitrary files. Additionally, if (and only if) the
default admindocs templates have been customized by the developers to
also expose the file contents, then not only the existence but also the
file contents would have been exposed.

As a mitigation, path sanitation is now applied and only files within
the template root directories can be loaded.

This issue has low severity, according to the Django security policy.

Thanks to Rasmus Lerchedahl Petersen and Rasmus Wriedt Larsen from the
CodeQL Python team for the report.

CVE-2021-33571: Possible indeterminate SSRF, RFI, and LFI attacks since
validators accepted leading zeros in IPv4 addresses
URLValidator, validate_ipv4_address(), and validate_ipv46_address()
didn't prohibit leading zeros in octal literals. If you used such values
you could suffer from indeterminate SSRF, RFI, and LFI attacks.

validate_ipv4_address() and validate_ipv46_address() validators were not
affected on Python 3.9.5+.

This issue has medium severity, according to the Django security policy.


Affected supported versions

Django main branch
Django 3.2
Django 3.1
Django 2.2


Resolution

Patches to resolve the issue have been applied to Django's main branch
and to the 3.2, 3.1, and 2.2 release branches. The patches may be
obtained from the following changesets.

CVE-2021-33203:

On the main branch
On the 3.2 release branch
On the 3.1 release branch
On the 2.2 release branch

CVE-2021-33571:

On the main branch
On the 3.2 release branch
On the 3.1 release branch
On the 2.2 release branch
The following releases have been issued:

Django 3.2.4 (download Django 3.2.4 | 3.2.4 checksums)
Django 3.1.12 (download Django 3.1.12 | 3.1.12 checksums)
Django 2.2.24 (download Django 2.2.24 | 2.2.24 checksums)
The PGP key ID used for these releases is Carlton Gibson: E17DF5C82B4F9D00.

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.



=========================================================
+ CERT-RENATER       |    tel : 01-53-94-20-44          +
+ 23/25 Rue Daviel   |    fax : 01-53-94-20-41          +
+ 75013 Paris        |    email:cert@support.renater.fr +
=========================================================