CVE-2022-24857
What it is
django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. Users are affected if they have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. The issue has been fixed in django-mfa3 0.5.0. It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition *before* the admin routes: url('admin/login/', lambda request: redirect(settings.LOGIN_URL)
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering.
- Exploit odds
- 1.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.2% in the next 30 days (EPSS).
- Severity: 7.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.2% · EPSS, next 30 days
- Weakness
- CWE-287 · Improper authentication
- Record status
- Modified
Affected
- django-mfa3 Project django-mfa3 < 0.5.0
Attack profile CVSS 3.1 · 7.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-24857.md and follow it. Check whether this project is affected by CVE-2022-24857. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de
- https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4
- https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de
- https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4
References
- https://github.com/xi/django-mfa3/blob/main/CHANGES.md#050-2022-04-15
- https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de
- https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4
- https://security.netapp.com/advisory/ntap-20220609-0003/
- https://github.com/xi/django-mfa3/blob/main/CHANGES.md#050-2022-04-15
- https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de
- https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4
- https://security.netapp.com/advisory/ntap-20220609-0003/