CVE-2024-53907: Django CVE-2024-53907 and CVE-2024-53908

Published Nov 28, 2024
·
Updated

An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The striptags() 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.

Affected Software

17 affected componentsFixes available
pip/django>=4.2<4.2.17
4.2.17
pip/django>=5.0<5.0.10
5.0.10
pip/django>=5.1<5.1.4
5.1.4
pip/django>=5.0.0<5.0.10
5.0.10
pip/django>=4.2.0<4.2.17
4.2.17
pip/django>=5.1.0<5.1.4
5.1.4
djangoproject Django>=4.2<4.2.17
djangoproject Django>=5.0<5.0.10
djangoproject Django>=5.1<5.1.4
debian/python-django<3:3.2.25-0+deb12u1
3:3.2.25-0+deb12u1
debian/python-django<3:4.2.17-1
3:4.2.17-1
debian/python-django<3:4.2.17-1
3:4.2.17-1
alpine/py3-django<4.2.20-r0
4.2.20-r0
alpine/py3-django<4.2.20-r0
4.2.20-r0
alpine/py3-django<4.2.20-r0
4.2.20-r0
alpine/py3-django<4.2.20-r0
4.2.20-r0
debian/python-django
3:3.2.25-0+deb12u33:3.2.25-0+deb12u63:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.17-23:5.2.19-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 4.2.17
  2. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 5.0.10
  3. Upgrade

    Upgrade pip/django to a version that resolves this vulnerability.

    Fixed in 5.1.4
  4. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.0.10
  5. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 4.2.17
  6. Upgrade

    Upgrade pip/Django to a version that resolves this vulnerability.

    Fixed in 5.1.4
  7. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u1
  8. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:4.2.17-1
  9. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 4.2.20-r0
  10. Upgrade

    Upgrade debian/python-django to a version that resolves this vulnerability.

    Fixed in 3:3.2.25-0+deb12u3Fixed in 3:3.2.25-0+deb12u6Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.17-2Fixed in 3:5.2.19-1
  11. Upgrade

    Upgrade django to a version that resolves this vulnerability.

    Fixed in 5.1.4
  12. Upgrade

    Upgrade django to a version that resolves this vulnerability.

    Fixed in 5.0.10
  13. Upgrade

    Upgrade django to a version that resolves this vulnerability.

    Fixed in 4.2.17

Event History

Nov 28, 2024
Data Sourced
via Red Hat·03:01 AM
DescriptionSeverityAffected Software
Dec 6, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·12:15 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·12:30 PM

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-53907?

CVE-2024-53907 has been classified as a potential denial-of-service vulnerability.

2

How do I fix CVE-2024-53907?

To mitigate CVE-2024-53907, upgrade to Django versions 5.1.4, 5.0.10, or 4.2.17 or later.

3

Which versions of Django are affected by CVE-2024-53907?

Django versions prior to 5.1.4, 5.0.10, and 4.2.17 are affected by CVE-2024-53907.

4

What methods are vulnerable in CVE-2024-53907?

The strip_tags() method and striptags template filter in Django are vulnerable due to specific inputs.

5

What types of attacks can CVE-2024-53907 result in?

CVE-2024-53907 can lead to denial-of-service attacks via large sequences of nested incomplete HTML entities.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203