Django Denial-of-service in django.utils.text.Truncator
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
4.2.6In Django 3.2 before 3.2.22, 4.1 before 4.1.12, and 4.2 before 4.2.6, the django.utils.text.Truncator chars() and words() methods (when used with html=True) are subject to a potential DoS (denial of service) attack via certain inputs with very long, potentially malformed HTML text. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which are thus also vulnerable. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232.
From the CVE record · mitre
Django's Truncator chars() and words() methods, and the truncatechars_html and truncatewords_html template filters that use them, are vulnerable when HTML truncation is enabled. Certain very long, potentially malformed HTML inputs can cause a denial of service. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check PyPI django installations running 3.2 before 3.2.22, 4.1 before 4.1.12, or 4.2 before 4.2.6, including affected prereleases.