Description

Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password and then leaves before entering their two-factor authentication code. The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' passwords are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' passwords are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis). This has been fixed in 1.12. After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas. In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used. As a workaround, wwitching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading.

Metrics

 

CVSS Version 4.0 CVSS Version 3.x CVSS Version 2.0

NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.

CVSS 4.0 Severity and Vector Strings:

NIST: NVD

N/A

NVD assessment not yet provided.

CVSS 3.x Severity and Vector Strings:

CNA:  GitHub, Inc.

Base Score:  5.4 MEDIUM

Vector:  CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

CVSS 2.0 Severity and Vector Strings:

NIST: NVD

Base Score:  3.6 LOW

Vector:  (AV:N/AC:H/Au:S/C:P/I:P/A:N)

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Hyperlink	Resource
https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08	Release Notes  Third Party Advisory
https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08	Release Notes  Third Party Advisory
https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359	Patch  Third Party Advisory
https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359	Patch  Third Party Advisory
https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf	Third Party Advisory
https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf	Third Party Advisory

Weakness Enumeration

CWE-ID	CWE Name	Source
CWE-312	Cleartext Storage of Sensitive Information	NIST   GitHub, Inc.

Known Affected Software Configurations Switch to CPE 2.2

CPEs loading, please wait.

Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.

Change History

3 change records found show changes

CVE Modified by CVE 11/21/2024 12:04:49 AM

Action	Type	Old Value	New Value
Added	Reference		https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08
Added	Reference		https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359
Added	Reference		https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf

CVE Modified by GitHub, Inc. 5/14/2024 2:29:53 AM

Action	Type	Old Value	New Value

Initial Analysis by NIST 7/21/2020 2:06:03 PM

Action	Type	Old Value	New Value
Added	CVSS V3.1		NIST AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
Added	CVSS V2		NIST (AV:N/AC:H/Au:S/C:P/I:P/A:N)
Added	CWE		NIST CWE-312
Added	CPE Configuration		OR *cpe:2.3:a:django_two-factor_authentication_project:django_two-factor_authentication:*:*:*:*:*:*:*:* versions up to (excluding) 1.12
Changed	Reference Type	https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08 No Types Assigned	https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08 Release Notes, Third Party Advisory
Changed	Reference Type	https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359 No Types Assigned	https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359 Patch, Third Party Advisory
Changed	Reference Type	https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf No Types Assigned	https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf Third Party Advisory
Added	CVSS V2 Metadata		Victim must voluntarily interact with attack mechanism