First published: Tue Sep 03 2024(Updated: )
An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/python-django | <=2:2.2.28-1~deb11u2<=3:3.2.19-1+deb12u1 | 3:4.2.16-1 |
Djangoproject Django | >=4.2.0<4.2.16 | |
Djangoproject Django | >=5.0<5.0.9 | |
Djangoproject Django | =5.1 | |
pip/Django | >=4.2<4.2.16 | 4.2.16 |
pip/Django | >=5.0<5.0.9 | 5.0.9 |
pip/Django | >=5.1<5.1.1 | 5.1.1 |
redhat/django | <5.1.1 | 5.1.1 |
redhat/django | <5.0.9 | 5.0.9 |
redhat/django | <4.2.16 | 4.2.16 |
IBM Storage Defender - Resiliency Service | <=2.0.0 - 2.0.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45230 is considered a potential denial-of-service vulnerability.
To fix CVE-2024-45230, update Django to version 5.1.1, 5.0.9, or 4.2.16.
Django versions prior to 5.1.1, 5.0.9, and 4.2.16 are affected by CVE-2024-45230.
CVE-2024-45230 affects installations of Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16.
The primary risk of CVE-2024-45230 is a potential denial-of-service attack through large inputs processed by the urlize() and urlizetrunc() filters.