Django security releases issued: 5.1.4, 5.0.10, and 4.2.17

In accordance with our security release policy, the Django team
is issuing releases for
Django 5.1.4,
Django 5.0.10, and
Django 4.2.17.
These releases address the security issues detailed below. We encourage all
users of Django to upgrade as soon as possible.

CVE-2024-53907: Potential denial-of-service in `django.utils.html.strip_tags()`

The strip_tags() method and striptags template filter are subject to a
potential denial-of-service attack via certain inputs containing large
sequences of nested incomplete HTML entities.

Thanks to jiangniao for the report.

This issue has severity “moderate” according to the Django security policy.

CVE-2024-53908: Potential SQL injection in `HasKey(lhs, rhs)` on Oracle

Direct usage of the django.db.models.fields.json.HasKey lookup on Oracle is
subject to SQL injection if untrusted data is used as a lhs value.
Applications that use the jsonfield.has_key lookup through the __ syntax are
unaffected.

Thanks to Seokchan Yoon for the report.

This issue has severity “high” according to the Django security policy.

Affected supported versions

Django main
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.

The PGP key ID used for this release is Sarah Boyce: 3955B19851EA96EF

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.

CVE-2024-53907: Potential denial-of-service in django.utils.html.strip_tags()

CVE-2024-53908: Potential SQL injection in HasKey(lhs, rhs) on Oracle