CVE-2022-42731

Public Exploit

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.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.10%
Third-Party Advisory github.com Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py#L58 third party advisory exploit
https://github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-release third party advisory release notes
https://github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-release third party advisory release notes

Frequently Asked Questions

What is the severity of CVE-2022-42731?
CVE-2022-42731 has been scored as a high severity vulnerability.
How to fix CVE-2022-42731?
To fix CVE-2022-42731, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-42731 being actively exploited in the wild?
It is possible that CVE-2022-42731 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.