CVE-2018-7536

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. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.

How to fix CVE-2018-7536

To remediate CVE-2018-7536, upgrade the affected package to a fixed version below.

• —upgrade to 1.11.11-r0 or later
• —upgrade to 1.11.11-r0 or later
• —upgrade to 1.7.11-1+deb8u3 or later
• —upgrade to 1.4.22-1+deb7u4 or later
• —upgrade to 1:1.11.11-1 or later
• —upgrade to 2.0.3 or later
• —upgrade to 1.8.19 or later

Is CVE-2018-7536 being exploited?

Low — EPSS is 1.4%, meaning exploitation activity has not been observed at scale.

Affected packages (7)

• from 0, < 1.11.11-r0
• from 0, < 1.11.11-r0
• from 0, < 1.7.11-1+deb8u3
• from 0, < 1.4.22-1+deb7u4
• from 0, < 1:1.11.11-1
• >= 2.0a1, < 2.0.3
• >= 1.8, < 1.8.19, >= 1.11, < 1.11.11, >= 2.0, < 2.0.3

CVSS scores

References (21)

• ADVISORYgithub.com/advisories/GHSA-r28v-mw67-m5p9
• ADVISORYnvd.nist.gov/vuln/detail/CVE-2018-7536
• ADVISORYsecurity.alpinelinux.org/vuln/CVE-2018-7536
• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2018-7536
• ADVISORY