| 1 |
========================== |
| 2 |
Django 5.1.1 release notes |
| 3 |
========================== |
| 4 |
|
| 5 |
*September 3, 2024* |
| 6 |
|
| 7 |
Django 5.1.1 fixes one security issue with severity "moderate", one security |
| 8 |
issue with severity "low", and several bugs in 5.1. |
| 9 |
|
| 10 |
CVE-2024-45230: Potential denial-of-service vulnerability in ``django.utils.html.urlize()`` |
| 11 |
=========================================================================================== |
| 12 |
|
| 13 |
:tfilter:`urlize` and :tfilter:`urlizetrunc` were subject to a potential |
| 14 |
denial-of-service attack via very large inputs with a specific sequence of |
| 15 |
characters. |
| 16 |
|
| 17 |
CVE-2024-45231: Potential user email enumeration via response status on password reset |
| 18 |
====================================================================================== |
| 19 |
|
| 20 |
Due to unhandled email sending failures, the |
| 21 |
:class:`~django.contrib.auth.forms.PasswordResetForm` class allowed remote |
| 22 |
attackers to enumerate user emails by issuing password reset requests and |
| 23 |
observing the outcomes. |
| 24 |
|
| 25 |
To mitigate this risk, exceptions occurring during password reset email sending |
| 26 |
are now handled and logged using the :ref:`django-contrib-auth-logger` logger. |
| 27 |
|
| 28 |
Bugfixes |
| 29 |
======== |
| 30 |
|
| 31 |
* Fixed a regression in Django 5.1 that caused a crash of ``Window()`` when |
| 32 |
passing an empty sequence to the ``order_by`` parameter, and a crash of |
| 33 |
``Prefetch()`` for a sliced queryset without ordering (:ticket:`35665`). |
| 34 |
|
| 35 |
* Fixed a regression in Django 5.1 where a new ``usable_password`` field was |
| 36 |
included in :class:`~django.contrib.auth.forms.BaseUserCreationForm` (and |
| 37 |
children). A new :class:`~django.contrib.auth.forms.AdminUserCreationForm` |
| 38 |
including this field was added, isolating the feature to the admin where it |
| 39 |
was intended (:ticket:`35678`). |
| 40 |
|
| 41 |
* Adjusted the deprecation warning ``stacklevel`` in :meth:`.Model.save` and |
| 42 |
:meth:`.Model.asave` to correctly point to the offending call site |
| 43 |
(:ticket:`35060`). |
| 44 |
|
| 45 |
* Adjusted the deprecation warning ``stacklevel`` when using ``OS_OPEN_FLAGS`` |
| 46 |
in :class:`~django.core.files.storage.FileSystemStorage` to correctly point |
| 47 |
to the offending call site (:ticket:`35326`). |
| 48 |
|
| 49 |
* Adjusted the deprecation warning ``stacklevel`` in |
| 50 |
``FieldCacheMixin.get_cache_name()`` to correctly point to the offending call |
| 51 |
site (:ticket:`35405`). |
| 52 |
|
| 53 |
* Restored, following a regression in Django 5.1, the ability to override the |
| 54 |
timezone and role setting behavior used within the ``init_connection_state`` |
| 55 |
method of the PostgreSQL backend (:ticket:`35688`). |
| 56 |
|
| 57 |
* Fixed a bug in Django 5.1 where variable lookup errors were logged when |
| 58 |
rendering admin fieldsets (:ticket:`35716`). |