| 1 |
=========================== |
| 2 |
Django 3.1.12 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*June 2, 2021* |
| 6 |
|
| 7 |
Django 3.1.12 fixes two security issues in 3.1.11. |
| 8 |
|
| 9 |
CVE-2021-33203: Potential directory traversal via ``admindocs`` |
| 10 |
=============================================================== |
| 11 |
|
| 12 |
Staff members could use the :mod:`~django.contrib.admindocs` |
| 13 |
``TemplateDetailView`` view to check the existence of arbitrary files. |
| 14 |
Additionally, if (and only if) the default admindocs templates have been |
| 15 |
customized by the developers to also expose the file contents, then not only |
| 16 |
the existence but also the file contents would have been exposed. |
| 17 |
|
| 18 |
As a mitigation, path sanitation is now applied and only files within the |
| 19 |
template root directories can be loaded. |
| 20 |
|
| 21 |
CVE-2021-33571: Possible indeterminate SSRF, RFI, and LFI attacks since validators accepted leading zeros in IPv4 addresses |
| 22 |
=========================================================================================================================== |
| 23 |
|
| 24 |
:class:`~django.core.validators.URLValidator`, |
| 25 |
:func:`~django.core.validators.validate_ipv4_address`, and |
| 26 |
:func:`~django.core.validators.validate_ipv46_address` didn't prohibit leading |
| 27 |
zeros in octal literals. If you used such values you could suffer from |
| 28 |
indeterminate SSRF, RFI, and LFI attacks. |
| 29 |
|
| 30 |
:func:`~django.core.validators.validate_ipv4_address` and |
| 31 |
:func:`~django.core.validators.validate_ipv46_address` validators were not |
| 32 |
affected on Python 3.9.5+. |