Django Two Factor Authentication
Vendor:
First CVE: Jul 10, 2020 · Active for 6 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.4
Avg CVSS
Higher Avg CVSS than 13% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Django Two Factor Authentication over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jul 10, 2020
6 years ago
Most Recent CVE
Jul 10, 2020
2,208 days ago
CVE Severity & Scoring
Django Two Factor Authentication1 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
Medium
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High1 (100.0%)
Unknown0 (0.0%)
User Interaction
None0 (0.0%)
Unknown0 (0.0%)
Required1 (100.0%)
Privileges Required
Low1 (100.0%)
High0 (0.0%)
None0 (0.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-15105MEDIUM 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 sub | Jul 10, 2020 | 5.4 | 20 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Django Two Factor Authentication
Top CWEs
Versions
No cataloged versions.