In accordance with our security release policy, the Django team
is issuing releases for
Django 5.1.1,
Django 5.0.9, and
Django 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 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
On the 5.1 branch
On the 5.0 branch
On the 4.2 branch
CVE-2024-45231: Potential user email enumeration via response status on password reset
On the main branch
On the 5.1 branch
On the 5.0 branch
On the 4.2 branch
The following releases have been issued
Django 5.1.1 (download Django 5.1.1 |
5.1.1 checksums)
Django 5.0.9 (download Django 5.0.9 |
5.0.9 checksums)
Django 4.2.16 (download Django 4.2.16 |
4.2.16 checksums)
The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E
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 for further information.