CVE-2024-45230: Django CVE-2024-45230 and CVE-2024-45231

Published Sep 3, 2024
·
Updated

An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.

Other sources

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

— IBM

urlize and urlizetrunc were subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.

— Red Hat

Affected Software

11 affected componentsFixes available
debian/python-django<=2:2.2.28-1~deb11u2, <=3:3.2.19-1+deb12u1
3:4.2.16-1
pip/Django>=4.2<4.2.16
4.2.16
pip/Django>=5.0<5.0.9
5.0.9
pip/Django>=5.1<5.1.1
5.1.1
djangoproject Django>=4.2.0<4.2.16
djangoproject Django>=5.0<5.0.9
djangoproject Django=5.1
IBM Storage Defender - Resiliency Service<=2.0.0 - 2.0.9
redhat/django<5.1.1
5.1.1
redhat/django<5.0.9
5.0.9
redhat/django<4.2.16
4.2.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3:4.2.16-1
  2. Upgrade

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

    Fixed in 4.2.16
  3. Upgrade

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

    Fixed in 5.0.9
  4. Upgrade

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

    Fixed in 5.1.1
  5. Upgrade

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

    Fixed in 5.1.1
  6. Upgrade

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

    Fixed in 5.0.9
  7. Upgrade

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

    Fixed in 4.2.16
  8. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.1.1
  9. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.0.9
  10. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.16
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2024-45230
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2024-45231

Event History

Sep 15, 2024
Data Sourced
via Ubuntu·07:06 PM
RemedyDescriptionSeverityAffected Software
Sep 24, 2024
Data Sourced
via Red Hat·07:42 PM
DescriptionSeverityAffected Software
Oct 8, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Advisory Published
via GitHub·06:33 PM
Dec 18, 2024
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-45230?

CVE-2024-45230 is considered a potential denial-of-service vulnerability.

2

How do I fix CVE-2024-45230?

To fix CVE-2024-45230, update Django to version 5.1.1, 5.0.9, or 4.2.16.

3

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

Django versions prior to 5.1.1, 5.0.9, and 4.2.16 are affected by CVE-2024-45230.

4

Does CVE-2024-45230 affect all Django installations?

CVE-2024-45230 affects installations of Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16.

5

What is the primary risk associated with CVE-2024-45230?

The primary risk of CVE-2024-45230 is a potential denial-of-service attack through large inputs processed by the urlize() and urlizetrunc() filters.

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