CVE-2022-42731
HIGHCVSS 7.5/10EPSS 1.00%
Last modified
CVE-2022-42731 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.. EPSS estimates a 1.00% chance of exploitation in the next 30 days.
Description
mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Django-Mfa2 Project | Django-Mfa2 | < 2.5.1 |
| Django-Mfa2 Project | Django-Mfa2 | >= 2.6.0, < 2.6.1 |
References
- https://github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py#L58Exploit, Third Party Advisory
- https://github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-releaseRelease Notes, Third Party Advisory
- https://github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-releaseRelease Notes, Third Party Advisory
- https://github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py#L58Exploit, Third Party Advisory
- https://github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-releaseRelease Notes, Third Party Advisory
- https://github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-releaseRelease Notes, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-42731?
mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage.
How severe is CVE-2022-42731?
CVE-2022-42731 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 1.00% probability of exploitation in the next 30 days.
How do I fix CVE-2022-42731?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- 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.
Related CVEs from 2022
- CVE-2022-42720Various refcounting bugs in the multi-BSS handling in the ma…7.8
- CVE-2022-42721A list management bug in BSS handling in the mac80211 stack …5.5
- CVE-2022-42722In the Linux kernel 5.8 through 5.19.x before 5.19.16, local…5.5
- CVE-2022-42724app/Controller/UsersController.php in MISP before 2.4.164 al…4.3
- CVE-2022-42725Warpinator through 1.2.14 allows access outside of an intend…7.5
- CVE-2022-4273A vulnerability, which was classified as critical, has been …9.8
- CVE-2022-42732A vulnerability has been identified in syngo Dynamics (All v…7.5
- CVE-2022-42733A vulnerability has been identified in syngo Dynamics (All v…7.5
- CVE-2022-42734A vulnerability has been identified in syngo Dynamics (All v…7.5
- CVE-2022-42735Improper Privilege Management vulnerability in Apache Softwa…8.8
- CVE-2022-42737Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2022-42738Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
Are you affected by CVE-2022-42731?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST