Django up to 1.11.22/2.1.10/2.2.3 Percent-Encoding input validation

Summaryinfo

A vulnerability has been found in Django up to 1.11.22/2.1.10/2.2.3 and classified as problematic. This vulnerability affects unknown code. The manipulation as part of Percent-Encoding leads to input validation. This vulnerability is listed as CVE-2019-14235. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Django up to 1.11.22/2.1.10/2.2.3 (Content Management System). It has been rated as problematic. This issue affects an unknown part. The manipulation as part of a Percent-Encoding leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is 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 passed certain inputs, django.utils.encoding.uri_to_iri could lead to significant memory usage due to a recursion when repercent-encoding invalid UTF-8 octet sequences.

The weakness was presented 08/02/2019 (Website). The advisory is shared at djangoproject.com. The identification of this vulnerability is CVE-2019-14235 since 07/22/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

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

See VDB-139371, VDB-139372 and VDB-139734 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion