Django up to 1.11.22/2.1.10/2.2.3 Regular Expression Slow input validation

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Django up to 1.11.22/2.1.10/2.2.3. Affected by this issue is some unknown functionality of the component Regular Expression. Performing a manipulation results in input validation (Slow). This vulnerability is identified as CVE-2019-14232. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Django up to 1.11.22/2.1.10/2.2.3 (Content Management System). It has been classified as problematic. This affects an unknown functionality of the component Regular Expression. The manipulation with an unknown input leads to a input validation vulnerability (Slow). CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on availability. The summary by CVE is:

An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.

The weakness was released 08/02/2019 (Website). It is possible to read the advisory at djangoproject.com. This vulnerability is uniquely identified as CVE-2019-14232 since 07/22/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 238025 (Debian dla-4210 : python-django-doc - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.11.23, 2.1.11 or 2.2.4 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (238025). Entries connected to this vulnerability are available at VDB-139372, VDB-139373 and VDB-139734. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• Django

Version

• 1.11.0
• 1.11.1
• 1.11.2
• 1.11.3
• 1.11.4
• 1.11.5
• 1.11.6
• 1.11.7
• 1.11.8
• 1.11.9
• 1.11.10
• 1.11.11
• 1.11.12
• 1.11.13
• 1.11.14
• 1.11.15
• 1.11.16
• 1.11.17
• 1.11.18
• 1.11.19
• 1.11.20
• 1.11.21
• 1.11.22
• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 2.1.6
• 2.1.7
• 2.1.8
• 2.1.9
• 2.1.10
• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion