CVE-2024-56374
MEDIUMCVE-2024-56374 is a medium-severity (CVSS 5.8) CWE-770 vulnerability in django. O3 Security confirms whether CVE-2024-56374 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Django has a potential denial-of-service vulnerability in IPv6 validation
Real-World Exposure
django🐍django🐍django🐍django🐍django🐍djangoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 5.1&&< 5.1.5 | 5.1.5 |
| 🐍PyPI | django | ≥ 5.0&&< 5.0.11 | 5.0.11 |
| 🐍PyPI | django | ≥ 4.2&&< 4.2.18 | 4.2.18 |
| 🐍PyPI | django | ≥ 5.1&&< 5.1.5 | 5.1.5 |
| 🐍PyPI | django | ≥ 5.0&&< 5.0.11 | 5.0.11 |
| 🐍PyPI | django | ≥ 4.2&&< 4.2.18 | 4.2.18 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update django to 5.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-56374 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-56374 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-56374. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-56374 in your dependencies?
O3 detects CVE-2024-56374 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.