Resource exhaustion in Djangoproject Django

CVE-2024-56374

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 clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 5.8 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L.

EPSS exploit prediction

EPSS: 0.019 (79.1th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 79th percentile — 79.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2024-56374: held from 0.019 to 0.019.

EPSS over last 30 days · oldest: 0.019 · newest: 0.019 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2024-56374?
CVE-2024-56374 is a medium-severity vulnerability in Djangoproject Django, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 5.8/10. Published 2025-01-14.
How severe is CVE-2024-56374?
Medium severity. CVSS v3 base score is 5.8 out of 10.
Is CVE-2024-56374 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.