CVE-2022-42731
Django-mfa2 Project Django-mfa2 vulnerability
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.
Affected products
Django-mfa2. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Django-mfa2 Project Django-mfa2 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py · Exploit
- github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-release · Third Party Advisory
- github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-release · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-42731
- github.com/pypa/advisory-database/tree/main/vulns/django-mfa2/PYSEC-2022-303.yaml
- github.com/mkalioby/django-mfa2/commit/54db5a513bcafa97a36e9f6dfa31d3c61fa8217b
- github.com/mkalioby/django-mfa2/commit/5fbb505e98ecdd409330a5c336ad5ec49631b0db
- github.com/advisories/GHSA-vw39-2wj9-4q86
- nvd.nist.gov/vuln/detail/CVE-2022-42731
- cve.org/CVERecord?id=CVE-2022-42731
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.