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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-14232US | high7.5 | — | ||
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 h… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.htmlWEB
- https://docs.djangoproject.com/en/dev/releases/security/WEB
- https://github.com/advisories/GHSA-c4qh-4vgv-qc6gADVISORY
- https://groups.google.com/forum/#!topic/django-announce/jIoju2-KLDsWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/STVX7X7IDWAH5SKE6MBMY3TEI6ZODBTK/WEB
- https://seclists.org/bugtraq/2019/Aug/15WEB
- https://security.gentoo.org/glsa/202004-17ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan