CVE-2024-56374: Django: Potential denial-of-service vulnerability in IPv6 validation

Published Jan 14, 2025
·
Updated

An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions cleanipv6address and isvalidipv6address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)

Other sources

An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions cleanipv6address and isvalidipv6address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)

MITRE

Affected Software

8 affected componentsFixes available
debian/python-django<=2:2.2.28-1~deb11u2, <=3:3.2.19-1+deb12u1
2:2.2.28-1~deb11u53:4.2.19-1
pip/Django>=4.2<4.2.18
4.2.18
pip/Django>=5.0<5.0.11
5.0.11
pip/Django>=5.1<5.1.5
5.1.5
djangoproject Django>=4.2<4.2.18
djangoproject Django>=5.0<5.0.11
djangoproject Django>=5.1<5.1.5
Debian Debian Linux=11.0

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 2:2.2.28-1~deb11u5Fixed in 3:4.2.19-1
  2. Upgrade

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

    Fixed in 4.2.18
  3. Upgrade

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

    Fixed in 5.0.11
  4. Upgrade

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

    Fixed in 5.1.5
  5. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.1.5
  6. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.0.11
  7. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 4.2.18
  8. Compensating control

    Apply mitigations for the IPv6 validation denial-of-service risk referenced by CVE-2024-56374 (e.g., constrain/limit request sizes or rates that reach Django’s IPv6 validation paths), since clean_ipv6_address / is_valid_ipv6_address and django.forms.GenericIPAddressField are affected.

Event History

Jan 14, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
Affected Software
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·09:31 PM
Jan 27, 2025
Data Sourced
via Ubuntu·12:42 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-56374?

CVE-2024-56374 is classified as a moderate severity vulnerability due to its potential for causing denial-of-service attacks.

2

How do I fix CVE-2024-56374?

To fix CVE-2024-56374, upgrade Django to version 5.1.5, 5.0.11, or 4.2.18, as appropriate.

3

Which Django versions are affected by CVE-2024-56374?

CVE-2024-56374 affects Django versions 4.2 before 4.2.18, 5.0 before 5.0.11, and 5.1 before 5.1.5.

4

What kind of attack can CVE-2024-56374 facilitate?

CVE-2024-56374 can potentially facilitate a denial-of-service attack through improper IPv6 validation.

5

Is there a workaround for CVE-2024-56374?

There is no official workaround for CVE-2024-56374, and the recommended action is to apply the necessary updates.

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