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
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
21 Nov 2024, 04:12
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securityfocus.com/bid/103357 - Third Party Advisory, VDB Entry | |
References | () https://access.redhat.com/errata/RHSA-2018:2927 - Third Party Advisory | |
References | () https://access.redhat.com/errata/RHSA-2019:0265 - Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2018/03/msg00006.html - Mailing List, Third Party Advisory | |
References | () https://usn.ubuntu.com/3591-1/ - Third Party Advisory | |
References | () https://www.debian.org/security/2018/dsa-4161 - Third Party Advisory | |
References | () https://www.djangoproject.com/weblog/2018/mar/06/security-releases/ - Release Notes, Vendor Advisory |
Information
Published : 2018-03-09 20:29
Updated : 2024-11-21 04:12
NVD link : CVE-2018-7537
Mitre link : CVE-2018-7537
CVE.ORG link : CVE-2018-7537
JSON object : View
Products Affected
canonical
- ubuntu_linux
djangoproject
- django
debian
- debian_linux
CWE
CWE-185
Incorrect Regular Expression