CVE-2024-38875: Django CVE-2024-38875, CVE-2024-39329, CVE-2024-39330, and CVE-2024-39614

Published Jul 5, 2024
·
Updated

An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.

Other sources

Django is vulnerable to a denial of service, caused by improper input validation by the urlize() and urlizetrunc() functions. By sending a specially crafted request using large number of brackets, a remote attacker could exploit this vulnerability to cause a denial of service condition.

— IBM

django.utils.html.urlize() was subject to a potential denial-of-service attack via certain inputs with a very large number of brackets.

Affected versions =================

Django main development branch Django 5.1 Django 5.0 Django 4.2

— Red Hat

Affected Software

14 affected componentsFixes available
pip/django>=5.0<5.0.7
5.0.7
pip/django>=4.2<4.2.14
4.2.14
IBM Storage Defender - Resiliency Service<=2.0.0 - 2.0.9
djangoproject Django>=4.2<4.2.14
djangoproject Django>=5.0<5.0.7
debian/python-django*
debian/python-django<3:4.2.14-1
3:4.2.14-1
debian/python-django<3:4.2.14-1
3:4.2.14-1
debian/python-django<=3:3.2.25-0+deb12u3, <=3:3.2.25-0+deb12u6
3:4.2.28-0+deb13u23:4.2.28-0+deb13u13:5.2.17-23:5.2.18-2
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0
alpine/py3-django<4.2.16-r0
4.2.16-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.0.7
  2. Upgrade

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

    Fixed in 4.2.14
  3. Upgrade

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

    Fixed in 3:4.2.14-1
  4. Upgrade

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

    Fixed in 3:4.2.28-0+deb13u2Fixed in 3:4.2.28-0+deb13u1Fixed in 3:5.2.17-2Fixed in 3:5.2.18-2
  5. Upgrade

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

    Fixed in 4.2.16-r0
  6. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.14
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.0.7

Event History

Jul 5, 2024
Data Sourced
via Red Hat·09:58 AM
DescriptionSeverityAffected Software
Jul 10, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·05:15 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:15 AM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·06:33 AM
Dec 18, 2024
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2024-38875?

CVE-2024-38875 has a severity that indicates a potential denial of service risk in affected versions of Django.

2

How do I fix CVE-2024-38875?

To fix CVE-2024-38875, upgrade to Django version 4.2.14 or 5.0.7 or later.

3

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

CVE-2024-38875 affects Django versions prior to 4.2.14 and 5.0 before 5.0.7.

4

What types of attacks are enabled by CVE-2024-38875?

CVE-2024-38875 may enable denial of service attacks through improper handling of inputs with numerous brackets.

5

Is there a specific recommendation for users of Django related to CVE-2024-38875?

Users of Django are advised to update their installations to the patched versions to mitigate the risks posed by CVE-2024-38875.

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