https://www.djangoproject.com/weblog/2024/sep/03/security-releases/
In accordance with `our security release policy <https://docs.djangoproject.com/en/dev/internals/security/>`_, the Django team is issuing releases for `Django 5.1.1 <https://docs.djangoproject.com/en/dev/releases/5.1.1/>`_, `Django 5.0.9 <https://docs.djangoproject.com/en/dev/releases/5.0.9/>`_, and `Django 4.2.16 <https://docs.djangoproject.com/en/dev/releases/4.2.16/>`_. These releases address the security issues detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2024-45230: Potential denial-of-service vulnerability in ``django.utils.html.urlize()`` =========================================================================================== ``urlize`` and ``urlizetrunc`` were subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters. Thanks to `MProgrammer <https://hackerone.com/mprogrammer>`_ for the report. This issue has severity "moderate" according to the Django security policy. CVE-2024-45231: Potential user email enumeration via response status on password reset ====================================================================================== Due to unhandled email sending failures, the ``django.contrib.auth.forms.PasswordResetForm`` class allowed remote attackers to enumerate user emails by issuing password reset requests and observing the outcomes. To mitigate this risk, exceptions occurring during password reset email sending are now handled and logged using the ``django.contrib.auth`` logger. Thanks to Thibaut Spriet for the report. This issue has severity "low" according to the Django security policy. Affected supported versions =========================== * Django main branch * Django 5.1 * Django 5.0 * Django 4.2 Resolution ========== Patches to resolve the issue have been applied to Django's main, 5.1, 5.0, and 4.2 branches. The patches may be obtained from the following changesets. CVE-2024-45230: Potential denial-of-service vulnerability in django.utils.html.urlize() --------------------------------------------------------------------------------------- * On the `main branch < https://github.com/django/django/commit/320dd27412e791e119d088281913d8f649617a13 >`__ * On the `5.1 branch < https://github.com/django/django/commit/022ab0a75c76ab2ea31dfcc5f2cf5501e378d397 >`__ * On the `5.0 branch < https://github.com/django/django/commit/813de2672bd7361e9a453ab62cd6e52f96b6525b >`__ * On the `4.2 branch < https://github.com/django/django/commit/d147a8ebbdf28c17cafbbe2884f0bc57e2bf82e2 >`__ CVE-2024-45231: Potential user email enumeration via response status on password reset -------------------------------------------------------------------------------------- * On the `main branch < https://github.com/django/django/commit/8c35a0a903fd979e3262fe300ca084ffbfb300d6 >`__ * On the `5.1 branch < https://github.com/django/django/commit/3c733c78d6f8e50296d6e248968b6516c92a53ca >`__ * On the `5.0 branch < https://github.com/django/django/commit/96d84047715ea1715b4bd1594e46122b8a77b9e2 >`__ * On the `4.2 branch < https://github.com/django/django/commit/bf4888d317ba4506d091eeac6e8b4f1fcc731199 >`__ The following releases have been issued ======================================= * Django 5.1.1 (`download Django 5.1.1 <https://www.djangoproject.com/m/releases/5.1/Django-5.1.1.tar.gz>`_ | `5.1.1 checksums <https://www.djangoproject.com/m/pgp/Django-5.1.1.checksum.txt>`_) * Django 5.0.9 (`download Django 5.0.9 <https://www.djangoproject.com/m/releases/5.0/Django-5.0.9.tar.gz>`_ | `5.0.9 checksums <https://www.djangoproject.com/m/pgp/Django-5.0.9.checksum.txt>`_) * Django 4.2.16 (`download Django 4.2.16 <https://www.djangoproject.com/m/releases/4.2/Django-4.2.16.tar.gz>`_ | `4.2.16 checksums <https://www.djangoproject.com/m/pgp/Django-4.2.16.checksum.txt>`_) The PGP key ID used for this release is Natalia Bidart: `2EE82A8D9470983E < https://github.com/nessita.gpg>`_ General notes regarding security reporting ========================================== As always, we ask that potential security issues be reported via private email to ``[email protected]``, and not via Django's Trac instance, nor via the Django Forum, nor via the django-developers list. Please see `our security policies <https://www.djangoproject.com/security/>`_ for further information.
