PatchTheCVEdjango two-factor authentication vulnerabilities and fixes
Recent CVEs affecting django two-factor authentication, with upgrade or downgrade steps. 1 tracked.
Also searched as: django two factor authentication, djangotwo-factorauthentication.
django two-factor authentication has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-07-10. Highest priority: CVE-2020-15105 (score 32/100).
- CVE-2020-15105 MEDIUM 5.4 UPGRADE Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (ba
FAQ
How do I fix django two-factor authentication vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is django two-factor authentication being exploited right now?
None of the tracked django two-factor authentication CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which django two-factor authentication CVE should I patch first?
CVE-2020-15105 currently ranks highest (32/100): Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (ba.