Vulnerability in Djangoproject Django

CVE-2018-7536

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

EPSS exploit prediction

EPSS: 0.046 (91.3th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 91st percentile — 91.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2018-7536: held from 0.045 to 0.046.

EPSS over last 30 days · oldest: 0.045 · newest: 0.046 · change: +0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2018-7536?
CVE-2018-7536 is a medium-severity vulnerability in Djangoproject Django, classified under Incorrect Regular Expression. CVSS score: 5.3/10. Published 2018-03-09.
How severe is CVE-2018-7536?
Medium severity. CVSS v3 base score is 5.3 out of 10.
Is CVE-2018-7536 known to be exploited?
3 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.