Vulnerability from bitnami_vulndb
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": [
{
"package": {
"ecosystem": "Bitnami",
"name": "django",
"purl": "pkg:bitnami/django"
},
"ranges": [
{
"events": [
{
"introduced": "4.2.0"
},
{
"fixed": "5.1.5"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2024-56374"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:djangoproject:django:*:*:*:*:*:python:*:*"
],
"severity": "High"
},
"details": "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.)",
"id": "BIT-django-2024-56374",
"modified": "2026-09-08T08:34:36.952Z",
"published": "2025-03-10T08:13:20.368Z",
"references": [
{
"type": "ADVISORY",
"url": "https://docs.djangoproject.com/en/dev/releases/security/"
},
{
"type": "ADVISORY",
"url": "https://groups.google.com/g/django-announce"
},
{
"type": "ADVISORY",
"url": "https://www.djangoproject.com/weblog/2025/jan/14/security-releases/"
},
{
"type": "ADVISORY",
"url": "http://www.openwall.com/lists/oss-security/2025/01/14/2"
},
{
"type": "ADVISORY",
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00024.html"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56374"
}
],
"schema_version": "1.5.0"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.