CVE-2022-42731: django-mfa2 vulnerable to MFA Replay attack
(updated )
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.
References
- github.com/advisories/GHSA-vw39-2wj9-4q86
- github.com/mkalioby/django-mfa2
- github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py
- github.com/mkalioby/django-mfa2/commit/54db5a513bcafa97a36e9f6dfa31d3c61fa8217b
- github.com/mkalioby/django-mfa2/commit/5fbb505e98ecdd409330a5c336ad5ec49631b0db
- github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-release
- github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-release
- github.com/pypa/advisory-database/tree/main/vulns/django-mfa2/PYSEC-2022-303.yaml
- nvd.nist.gov/vuln/detail/CVE-2022-42731
Code Behaviors & Features
Detect and mitigate CVE-2022-42731 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →