Severity
Severity not reported.
Affected versions
| Affected | Fixed in |
|---|---|
1.11 to before 1.11.23 | 1.11.23Advisories → |
2.1 to before 2.1.11 | 2.1.11Advisories → |
2.2 to before 2.2.4 | 2.2.4Advisories → |
Description
An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
References
- ARTICLEwww.djangoproject.com/weblog/2019/aug/01/security-releases/ ↗
- Webdocs.djangoproject.com/en/dev/releases/security/ ↗
- Webgroups.google.com/forum/#!topic/django-announce/jIoju2-KLDs ↗
- Weblists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html ↗
- Webseclists.org/bugtraq/2019/Aug/15 ↗
- Advisorywww.debian.org/security/2019/dsa-4498 ↗
- Weblists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html ↗
- Weblists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/STVX7X7IDWAH5SKE6MBMY3TEI6ZODBTK/ ↗
- Advisorysecurity.netapp.com/advisory/ntap-20190828-0002/ ↗
- Advisorysecurity.gentoo.org/glsa/202004-17 ↗
- Advisorygithub.com/advisories/GHSA-c4qh-4vgv-qc6g ↗