Django up to 1.8.18/1.11.10/2.0.2 Regex Backtracking incorrect regex

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in Django up to 1.8.18/1.11.10/2.0.2. This issue affects some unknown processing of the component Regex Handler. Such manipulation leads to incorrect regex (Backtracking). This vulnerability is listed as CVE-2018-7536. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Django up to 1.8.18/1.11.10/2.0.2 (Content Management System). Affected by this issue is an unknown function of the component Regex Handler. The manipulation with an unknown input leads to a incorrect regex vulnerability (Backtracking). Using CWE to declare the problem leads to CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. Impacted is availability. CVE summarizes:

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.

The bug was discovered 03/06/2018. The weakness was presented 03/09/2018 (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2018-7536 since 02/26/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 108640 (openSUSE Security Update : python-Django (openSUSE-2018-317)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 277250 (Fedora Security Update for python-django (FEDORA-2018-bd1147f152)).

Upgrading to version 1.8.19, 1.11.11 or 2.0.3 eliminates this vulnerability. A possible mitigation has been published 3 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (108640) and SecurityFocus (BID 103361†). See VDB-114339 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Backtracking
Class: Incorrect regex / Backtracking
CWE: CWE-185 / CWE-697
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 108640
Nessus Name: openSUSE Security Update : python-Django (openSUSE-2018-317)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 830268
OpenVAS Name: Debian Security Advisory DSA 4161-1 (python-django - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Django 1.8.19/1.11.11/2.0.3

Timelineinfo

02/26/2018 🔍
03/06/2018 +8 days 🔍
03/09/2018 +3 days 🔍
03/09/2018 +0 days 🔍
03/10/2018 +1 days 🔍
03/27/2018 +17 days 🔍
03/27/2018 +0 days 🔍
02/21/2023 +1792 days 🔍

Sourcesinfo

Advisory: RHSA-2018:2927⛔
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-7536 (🔍)
GCVE (CVE): GCVE-0-2018-7536
GCVE (VulDB): GCVE-100-114338

OVAL: 🔍

SecurityFocus: 103361

See also: 🔍

Entryinfo

Created: 03/10/2018 23:05
Updated: 02/21/2023 08:40
Changes: 03/10/2018 23:05 (78), 01/12/2020 10:10 (3), 02/21/2023 08:40 (4)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!