Severity
- CVSS 3.x
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| 6a0dc2176f4ebf907e124d433411e52bba39a28e to before c686dd8e6bb3817bcf04b8f13c025b4d3c3dc6dc | c686dd8e6bb3817bcf04b8f13c025b4d3c3dc6dc |
| c669cf279ae7b3e02a61db4fb077030a4db80e4f to before 1cc5aceac0a73468a6d1a671b9c86423e5bcf011 | 1cc5aceac0a73468a6d1a671b9c86423e5bcf011 |
| 8c85c8692240e5ae4b568eb4272475fe1fa4b059 to before 2d73ffc6f96e399716a1ed3f58acd4e99afa3d33 | 2d73ffc6f96e399716a1ed3f58acd4e99afa3d33 |
Description
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. 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
- Advisorywww.securityfocus.com/bid/103357 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2018:2927 ↗
- Advisoryaccess.redhat.com/errata/RHSA-2019:0265 ↗
- Advisorylists.debian.org/debian-lts-announce/2018/03/msg00006.html ↗
- Advisoryusn.ubuntu.com/3591-1/ ↗
- Advisorywww.debian.org/security/2018/dsa-4161 ↗
- Advisorywww.djangoproject.com/weblog/2018/mar/06/security-releases/ ↗