| 1 |
=========================== |
| 2 |
Django 5.0.9 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*September 3, 2024* |
| 6 |
|
| 7 |
Django 5.0.9 fixes one security issue with severity "moderate" and one security |
| 8 |
issue with severity "low" in 5.0.8. |
| 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. |