CVE-2022-42731 django-mfa2 vulnerable to MFA Replay attack
Attackers can replay device registration challenges to register unauthorized devices, potentially leading to account takeover in django-mfa2.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-42731?
CVE-2022-42731 is a high-severity vulnerability in n/a, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-294
Which versions are affected by CVE-2022-42731?
5 open source packages ship an affected version, including django-mfa2. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django-mfa2 PyPI | All versions | 2.5.1, 2.6.1 |
django-mfa2 PyPI | All versions | 2.5.1 |
django-mfa2 PyPI | All versions | 2.5.1 |
django-mfa2 PyPI | From 2.6.0 | 2.6.1 |
django-mfa2 PyPI | From 2.6.0 | 2.6.1 |
Products include Django-Mfa2 Project Django-Mfa2.
How do I fix CVE-2022-42731?
Upgrade django-mfa2 to a fixed version for your release line: 2.5.1 or 2.6.1.
Is CVE-2022-42731 being exploited?
There is no known exploitation of CVE-2022-42731 in the wild and no public exploit code.
Sources
Also known as GHSA-vw39-2wj9-4q86, PYSEC-2022-303.