CVE-2018-7536
moderate-risk
Published 2018-03-09
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.
Do I need to act?
~
1.4% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10
Medium
NETWORK
/ LOW complexity
Affected Products (9)
Affected Vendors
References (24)
Third Party Advisory
http://www.securityfocus.com/bid/103361
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:2927
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0051
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0082
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0265
Third Party Advisory
https://usn.ubuntu.com/3591-1/
Third Party Advisory
https://www.debian.org/security/2018/dsa-4161
Third Party Advisory
http://www.securityfocus.com/bid/103361
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:2927
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0051
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0082
Third Party Advisory
https://access.redhat.com/errata/RHSA-2019:0265
and 4 more references
40
/ 100
moderate-risk
Severity
21/34 · High
Exploitability
4/34 · Minimal
Exposure
15/34 · Moderate