CVE-2024-41989: Django CVE-2024-41989, CVE-2024-41990, CVE-2024-41991, and CVE-2024-42005

Published Aug 2, 2024
·
Updated

An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The floatformat template filter is subject to significant memory consumption when given a string representation of a number in scientific notation with a large exponent.

Other sources

Description: If floatformat received a string representation of a number in scientific notation with a large exponent, it could lead to significant memory consumption.

To avoid this, decimals with more than 200 digits are now returned as is.

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

Django main development branch Django 5.1 (currently at release candidate status) Django 5.0 Django 4.2

— Red Hat

Django is vulnerable to a denial of service, caused by a memory exhaustion in django.utils.numberformat.floatformat() method. By sending a vspecially crafted request, a remote attacker could exploit this vulnerability to cause a denial of service.

— IBM

Affected Software

14 affected componentsFixes available
pip/django>=4.2<4.2.15
4.2.15
pip/django>=5.0<5.0.8
5.0.8
IBM Storage Defender - Resiliency Service<=2.0.0 - 2.0.9
djangoproject Django>=4.2<4.2.15
djangoproject Django>=5.0<5.0.8
debian/python-django<3:3.2.25-0+deb12u1
3:3.2.25-0+deb12u1
debian/python-django<3:4.2.15-1
3:4.2.15-1
debian/python-django<3:4.2.15-1
3:4.2.15-1
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
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.15
  2. Upgrade

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

    Fixed in 5.0.8
  3. Upgrade

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

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

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

    Fixed in 3:4.2.15-1
  5. Upgrade

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

    Fixed in 4.2.16-r0
  6. 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
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.0.8
  8. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.15

Event History

Aug 2, 2024
Data Sourced
via Red Hat·01:45 AM
DescriptionSeverityAffected Software
Aug 7, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·03:30 PM
Dec 18, 2024
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

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-41989?

CVE-2024-41989 has a high severity rating due to the potential for significant memory consumption.

2

How do I fix CVE-2024-41989?

To fix CVE-2024-41989, update Django to version 4.2.15 or 5.0.8 or later.

3

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

CVE-2024-41989 affects Django versions before 5.0.8 and 4.2 before 4.2.15.

4

What impact does CVE-2024-41989 have on applications?

CVE-2024-41989 can lead to application instability due to excessive memory consumption resulting from certain input.

5

Is there a workaround for CVE-2024-41989?

There is no officially recommended workaround for CVE-2024-41989; upgrading to a patched version is necessary.

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