django-mfa2 up to 2.5.0/2.6.0 Device Registration mfa/FIDO2.py authentication replay
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in django-mfa2 up to 2.5.0/2.6.0. This vulnerability affects unknown code of the file mfa/FIDO2.py of the component Device Registration Handler. The manipulation results in authentication replay. This vulnerability is cataloged as CVE-2022-42731. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in django-mfa2 up to 2.5.0/2.6.0 (Content Management System). It has been classified as critical. Affected is an unknown part of the file mfa/FIDO2.py of the component Device Registration Handler. The manipulation with an unknown input leads to a authentication replay vulnerability. CWE is classifying the issue as CWE-294. A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was shared 10/11/2022. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2022-42731 since 10/10/2022. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1040.
Upgrading to version 2.5.1 or 2.6.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Authentication replayCWE: CWE-294 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: django-mfa2 2.5.1/2.6.1
Timeline
10/10/2022 🔍10/11/2022 🔍
10/11/2022 🔍
05/20/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2022-42731 (🔍)
GCVE (CVE): GCVE-0-2022-42731
GCVE (VulDB): GCVE-100-210444
Entry
Created: 10/11/2022 19:46Updated: 05/20/2025 16:32
Changes: 10/11/2022 19:46 (42), 11/05/2022 09:43 (11), 05/20/2025 16:32 (15)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.