CVE-2024-39614: 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 5.0 before 5.0.7 and 4.2 before 4.2.14. getsupportedlanguagevariant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.

Other sources

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. getsupportedlanguagevariant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.

— NVD

getsupportedlanguagevariant() was subject to a potential denial-of-service attack when used with very long strings including a specific set of characters.

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

Django main development branch Django 5.1 Django 5.0 Django 4.2

— Red Hat

Affected Software

6 affected componentsFixes available
pip/Django>=4.2<4.2.14
4.2.14
pip/Django>=5.0<5.0.7
5.0.7
debian/python-django<=2:2.2.28-1~deb11u2, <=3:3.2.19-1+deb12u1
3:4.2.16-1
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

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.14
  2. Upgrade

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

    Fixed in 5.0.7
  3. Upgrade

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

    Fixed in 3:4.2.16-1
  4. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.0.7
  5. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.14

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
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 AM
Affected Software
Advisory Published
via GitHub·06:33 AM
Sep 15, 2024
Data Sourced
via Ubuntu·07:46 PM
RemedyDescriptionSeverityAffected Software
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-39614?

CVE-2024-39614 has a severity rating that indicates a potential denial-of-service attack vulnerability.

2

How do I fix CVE-2024-39614?

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

3

What versions of Django are affected by CVE-2024-39614?

CVE-2024-39614 affects Django 5.0 prior to 5.0.7 and 4.2 prior to 4.2.14.

4

Can CVE-2024-39614 affect my applications?

Yes, CVE-2024-39614 can affect applications that use the vulnerable versions of Django and may lead to denial-of-service.

5

Is there a workaround for CVE-2024-39614?

There is no documented workaround for CVE-2024-39614; upgrading to the fixed versions is recommended.

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