Detections
Analytics
SCA: security update for django-two-factor-auth (GHSA-vhr6-pvjm-9qwf)
medium Tenable Cloud Security Plugin ID 419362
Description
There are packages installed that are affected by a vulnerability referenced in the following CVE:- 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. (CVE-2020-15105)
See Also
Plugin Details
Severity: Medium
ID: 419362
Version: Revision 1.8
Type: Local
Family: SCA Checks
Published: 1/23/2025
Updated: 7/2/2026
Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security
Risk Information
VPR
Risk Factor: Low
Score: 3.5
Percentile: 51.63
Vendor
Vendor Severity: Medium
CVSS v2
Risk Factor: Low
Base Score: 3.6
Temporal Score: 2.7
Vector: CVSS2#AV:N/AC:H/Au:S/C:P/I:P/A:N
CVSS Score Source: CVE-2020-15105
CVSS v3
Risk Factor: Medium
Base Score: 5.4
Temporal Score: 4.7
Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C
CVSS v4
Risk Factor: Medium
Base Score: 6
Threat Score: 2.3
Threat Vector: CVSS:4.0/E:U
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Vulnerability Information
Exploit Ease: No known exploits are available
Patch Publication Date: 7/10/2020
Vulnerability Publication Date: 7/10/2020
Reference Information
CVE: CVE-2020-15105
cwe: CWE-312