Vulnerability advisory
CVE-2023-46695
Also known as BIT-django-2023-46695GHSA-qmf9-6jqf-j8fqPYSEC-2023-222
Severity
Severity not reported.
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| 3591e1c1acbd7c13174275367c3fdf012cb0413b to before 60e648a7ae033a9c2d1ab23a58402f57a1754df1 | 60e648a7ae033a9c2d1ab23a58402f57a1754df1 |
| 9fee86e44dd83dc968ec443adcde191b3eba1286 to before 42591a8aeb48f3cdf7da9fd0631017dd5410525a | 42591a8aeb48f3cdf7da9fd0631017dd5410525a |
| 97aa3b7f08f51669e118f3af5ca91026e39664c3 to before d254a54e7f65e83d8971bd817031bc6af32a7a46 | d254a54e7f65e83d8971bd817031bc6af32a7a46 |
Description
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.
References
- Webdocs.djangoproject.com/en/4.2/releases/security/ ↗
- Webgroups.google.com/forum/#%21forum/django-announce ↗
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2023/46xxx/CVE-2023-46695.json ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-46695 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20231214-0001/ ↗
- ARTICLEwww.djangoproject.com/weblog/2023/nov/01/security-releases/ ↗