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: 2025-01-14 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-56374 is rated Moderate Risk (51.7/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.85%). EPSS rose +1.77% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-56374

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.08% 1.85% +1.77%
2 2026-02-22 0.60% 0.08% -0.52%
3 2026-02-19 — 0.60% —

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56374

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-56374

GitHub Security Advisory for CVE-2024-56374

GHSA-qcgg-j2x8-h9g8 · Severity: medium · Ecosystem: pip — Django has a potential denial-of-service vulnerability in IPv6 validation

OS Trackers for CVE-2024-56374

vendor priority summary link
alpine — CVE-2024-56374: 1 source package rows (py3-django); 3 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2024-56374
debian not yet assigned CVE-2024-56374 not yet assigned priority: Debian including 1 source packages (python-django), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-56374
gentoo normal CVE-2024-56374: 1 GLSA(s) (202509-03), 1 atom(s) (dev-python/django); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-56374
redhat medium — https://access.redhat.com/security/cve/CVE-2024-56374
suse high CVE-2024-56374 severity important: SUSE including 11 source package names (python3-Django-2.2.28-bp156.6.1, python311-Django-4.2.11-150600.3.15.1, …), 18 product×package rows across 10 product lines (Image SLE-Micro, Image SLE-Micro-BYOS, … (10 product lines)): Fixed 18. https://www.suse.com/security/cve/CVE-2024-56374/
ubuntu medium CVE-2024-56374 medium priority: Ubuntu including 1 source packages (python-django), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): released 7, needs-triage 3. https://ubuntu.com/security/CVE-2024-56374

Affected software / configurations for CVE-2024-56374

Vendor Product Version Raw CPE
djangoproject django >= 4.2, < 4.2.18 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.0, < 5.0.11 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
djangoproject django >= 5.1, < 5.1.5 cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2024-56374

cvelogic Threat Intelligence