Vulnerability advisory

PYSEC-2025-1

Published Jan 14, 2025Updated Jun 10, 2026OSV record ↗

Also known as BIT-django-2024-56374CVE-2024-56374GHSA-qcgg-j2x8-h9g8

Severity

Severity not reported.

Affected versions

django PyPI

Affected	Fixed in
`5.1` to before 5.1.5	`5.1.5`Advisories →
`5.0` to before 5.0.11	`5.0.11`Advisories →
`4.2` to before 4.2.18	`4.2.18`Advisories →
Also listed as affected (34) `4.2` `4.2.1` `4.2.10` `4.2.11` `4.2.12` `4.2.13` `4.2.14` `4.2.15` `4.2.16` `4.2.17` `4.2.2` `4.2.3` `4.2.4` `4.2.5` `4.2.6` `4.2.7` `4.2.8` `4.2.9` `5.0` `5.0.1` `5.0.10` `5.0.2` `5.0.3` `5.0.4` `5.0.5` `5.0.6` `5.0.7` `5.0.8` `5.0.9` `5.1` `5.1.1` `5.1.2` `5.1.3` `5.1.4`

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.)

PYSEC-2025-1

Affected versions

django PyPI

Description

References