| 1 |
========================== |
| 2 |
Django 5.0.7 release notes |
| 3 |
========================== |
| 4 |
|
| 5 |
*July 9, 2024* |
| 6 |
|
| 7 |
Django 5.0.7 fixes two security issues with severity "moderate", two security |
| 8 |
issues with severity "low", and one bug in 5.0.6. |
| 9 |
|
| 10 |
CVE-2024-38875: 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 certain inputs with a very large number of |
| 15 |
brackets. |
| 16 |
|
| 17 |
CVE-2024-39329: Username enumeration through timing difference for users with unusable passwords |
| 18 |
================================================================================================ |
| 19 |
|
| 20 |
The :meth:`~django.contrib.auth.backends.ModelBackend.authenticate()` method |
| 21 |
allowed remote attackers to enumerate users via a timing attack involving login |
| 22 |
requests for users with unusable passwords. |
| 23 |
|
| 24 |
CVE-2024-39330: Potential directory-traversal via ``Storage.save()`` |
| 25 |
==================================================================== |
| 26 |
|
| 27 |
Derived classes of the :class:`~django.core.files.storage.Storage` base class |
| 28 |
which override :meth:`generate_filename() |
| 29 |
<django.core.files.storage.Storage.generate_filename()>` without replicating |
| 30 |
the file path validations existing in the parent class, allowed for potential |
| 31 |
directory-traversal via certain inputs when calling :meth:`save() |
| 32 |
<django.core.files.storage.Storage.save()>`. |
| 33 |
|
| 34 |
Built-in ``Storage`` sub-classes were not affected by this vulnerability. |
| 35 |
|
| 36 |
CVE-2024-39614: Potential denial-of-service vulnerability in ``get_supported_language_variant()`` |
| 37 |
================================================================================================= |
| 38 |
|
| 39 |
:meth:`~django.utils.translation.get_supported_language_variant` was subject to |
| 40 |
a potential denial-of-service attack when used with very long strings |
| 41 |
containing specific characters. |
| 42 |
|
| 43 |
To mitigate this vulnerability, the language code provided to |
| 44 |
:meth:`~django.utils.translation.get_supported_language_variant` is now parsed |
| 45 |
up to a maximum length of 500 characters. |
| 46 |
|
| 47 |
When the language code is over 500 characters, a :exc:`ValueError` will now be |
| 48 |
raised if ``strict`` is ``True``, or if there is no generic variant and |
| 49 |
``strict`` is ``False``. |
| 50 |
|
| 51 |
Bugfixes |
| 52 |
======== |
| 53 |
|
| 54 |
* Fixed a bug in Django 5.0 that caused a crash of ``Model.full_clean()`` on |
| 55 |
unsaved model instances with a ``GeneratedField`` and certain defined |
| 56 |
:attr:`Meta.constraints <django.db.models.Options.constraints>` |
| 57 |
(:ticket:`35560`). |