CVE-2020-15105

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.

• CWE-312
• CWE-312

• https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08Release Notes, Third Party Advisory
• https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359Patch, Third Party Advisory
• https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwfThird Party Advisory
• https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08Release Notes, Third Party Advisory
• https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359Patch, Third Party Advisory
• https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwfThird Party Advisory

Published

Jul 10, 2020

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2020-1510An information disclosure vulnerability exists when the win3…5.5
• CVE-2020-15100In freewvs before 0.1.1, a user could create a large file th…3.3
• CVE-2020-15101In freewvs before 0.1.1, a directory structure of more than …3.3
• CVE-2020-15102In PrestaShop Dashboard Productions before version 2.1.0, th…6.5
• CVE-2020-15103In FreeRDP less than or equal to 2.1.2, an integer overflow …3.5
• CVE-2020-15104In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 …5.4
• CVE-2020-15106In etcd before versions 3.3.23 and 3.4.10, a large slice cau…6.5
• CVE-2020-15107In openenclave before 0.10.0, enclaves that use x87 FPU oper…5.3
• CVE-2020-15108In glpi before 9.5.1, there is a SQL injection for all usage…7.1
• CVE-2020-15109In solidus before versions 2.8.6, 2.9.6, and 2.10.2, there i…5.3
• CVE-2020-1511An elevation of privilege vulnerability exists when Connecte…7.8
• CVE-2020-15110In jupyterhub-kubespawner before 0.12, certain usernames wil…8.1