CVE-2018-7536Not scoredCWE-185

CVE-2018-7536: Djangoproject vulnerability

Djangoproject · Django

Vendor fix available · Affected: Djangoproject · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

4.5%probability of exploitation in the next 30 days

91st percentile

050100

Higher than 91% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Incorrect Regular Expression · Input Validation and Logic
Vendor: Djangoproject
Published: March 2018
Band: Possible (1 to 10%), March 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2018-7536 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.