First published: Tue Jan 14 2025(Updated: )
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 Software | Affected Version | How to fix |
---|---|---|
Django | <5.1.5 | |
Django | <5.0.11 | |
Django | <4.2.18 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2337996 is classified as a potential denial-of-service vulnerability.
Django versions before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18 are affected by REDHAT-BUG-2337996.
To fix REDHAT-BUG-2337996, upgrade Django to version 5.1.5 or later, 5.0.11 or later, or 4.2.18 or later.
REDHAT-BUG-2337996 could allow a potential denial-of-service attack due to a lack of upper-bound limit enforcement in IPv6 validation.
The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are involved in the REDHAT-BUG-2337996 vulnerability.