First published: Wed Nov 01 2023(Updated: )
An issue was discovered in Django 3.2 before 3.2.23, 4.1 before 4.1.13, and 4.2 before 4.2.7. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.forms.UsernameField is subject to a potential DoS (denial of service) attack via certain inputs with a very large number of Unicode characters.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | >=3.2<3.2.23 | |
Djangoproject Django | >=4.1<4.1.13 | |
Djangoproject Django | >=4.2.<4.2.7 | |
pip/Django | >=4.2a1<4.2.7 | 4.2.7 |
pip/Django | >=4.1a1<4.1.13 | 4.1.13 |
pip/Django | >=3.2a1<3.2.23 | 3.2.23 |
>=3.2<3.2.23 | ||
>=4.1<4.1.13 | ||
>=4.2.<4.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Django vulnerability is CVE-2023-46695.
The title of this Django vulnerability is 'Potential denial of service vulnerability in UsernameField on Windows'.
The severity level of this Django vulnerability is not mentioned in the provided information. Please refer to the provided references for more details.
To fix this Django vulnerability, update Django to version 3.2.23, 4.1.13, or 4.2.7 depending on your current version.
You can find more information about this Django vulnerability in the provided references.