Django up to 1.11.18/2.0.10/2.1.5 django.utils.numberformat.format resource consumption

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Django up to 1.11.18/2.0.10/2.1.5. Affected by this issue is the function django.utils.numberformat.format. This manipulation causes resource consumption. This vulnerability is tracked as CVE-2019-6975. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Django up to 1.11.18/2.0.10/2.1.5 (Content Management System) and classified as problematic. Affected by this vulnerability is the function django.utils.numberformat.format. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the django.utils.numberformat.format() function.

The bug was discovered 02/11/2019. The weakness was disclosed 02/11/2019 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is known as CVE-2019-6975 since 01/26/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The commercial vulnerability scanner Qualys is able to test this issue with plugin 277739 (Fedora Security Update for python2-django1 (FEDORA-2019-5ad2149e99)).

Upgrading to version 1.11.19, 2.0.11 or 2.1.6 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106453†). The entry VDB-128980 is pretty similar. 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
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5

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