Django up to 1.11.26/2.2.8/3.0.0 Password Reset password recovery

Summaryinfo

A vulnerability marked as critical has been reported in Django up to 1.11.26/2.2.8/3.0.0. This affects an unknown part of the component Password Reset. Performing a manipulation results in password recovery. This vulnerability is identified as CVE-2019-19844. The attack can be initiated remotely. Additionally, an exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Django up to 1.11.26/2.2.8/3.0.0 (Content Management System). This affects an unknown code of the component Password Reset. The manipulation with an unknown input leads to a password recovery vulnerability. CWE is classifying the issue as CWE-640. The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)

The weakness was released 12/18/2019. This vulnerability is uniquely identified as CVE-2019-19844. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.

Upgrading to version 1.11.27, 2.2.9 or 3.0.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (47879). 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
• 1.11.23
• 1.11.24
• 1.11.25
• 1.11.26
• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7
• 2.2.8
• 3.0

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