Django potential denial of service vulnerability in UsernameField on Windows
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
4.2.7An 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.
From the CVE record · mitre
On Windows, slow NFKC normalization makes django.contrib.auth.forms.UsernameField vulnerable to potential denial of service when it processes certain inputs containing very large numbers of Unicode characters. The input does not specify whether authentication or user interaction is required.
Check Windows deployments using Django 3.2 before 3.2.23, 4.1 before 4.1.13, or 4.2 before 4.2.7, including affected prereleases.