| 1 |
=========================== |
| 2 |
Django 2.2.26 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*January 4, 2022* |
| 6 |
|
| 7 |
Django 2.2.26 fixes one security issue with severity "medium" and two security |
| 8 |
issues with severity "low" in 2.2.25. |
| 9 |
|
| 10 |
CVE-2021-45115: Denial-of-service possibility in ``UserAttributeSimilarityValidator`` |
| 11 |
===================================================================================== |
| 12 |
|
| 13 |
:class:`.UserAttributeSimilarityValidator` incurred significant overhead |
| 14 |
evaluating submitted password that were artificially large in relative to the |
| 15 |
comparison values. On the assumption that access to user registration was |
| 16 |
unrestricted this provided a potential vector for a denial-of-service attack. |
| 17 |
|
| 18 |
In order to mitigate this issue, relatively long values are now ignored by |
| 19 |
``UserAttributeSimilarityValidator``. |
| 20 |
|
| 21 |
This issue has severity "medium" according to the :ref:`Django security policy |
| 22 |
<severity-levels>`. |
| 23 |
|
| 24 |
CVE-2021-45116: Potential information disclosure in ``dictsort`` template filter |
| 25 |
================================================================================ |
| 26 |
|
| 27 |
Due to leveraging the Django Template Language's variable resolution logic, the |
| 28 |
:tfilter:`dictsort` template filter was potentially vulnerable to information |
| 29 |
disclosure or unintended method calls, if passed a suitably crafted key. |
| 30 |
|
| 31 |
In order to avoid this possibility, ``dictsort`` now works with a restricted |
| 32 |
resolution logic, that will not call methods, nor allow indexing on |
| 33 |
dictionaries. |
| 34 |
|
| 35 |
As a reminder, all untrusted user input should be validated before use. |
| 36 |
|
| 37 |
This issue has severity "low" according to the :ref:`Django security policy |
| 38 |
<severity-levels>`. |
| 39 |
|
| 40 |
CVE-2021-45452: Potential directory-traversal via ``Storage.save()`` |
| 41 |
==================================================================== |
| 42 |
|
| 43 |
``Storage.save()`` allowed directory-traversal if directly passed suitably |
| 44 |
crafted file names. |
| 45 |
|
| 46 |
This issue has severity "low" according to the :ref:`Django security policy |
| 47 |
<severity-levels>`. |