{"answers":{"affected":"3 open source packages ship an affected version, including django-mfa3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24857 in the wild and no public exploit code.","fix":"Upgrade django-mfa3 to 0.5.0 or later.","what":"CVE-2022-24857 is a high-severity authentication bypass vulnerability in xi django-mfa3, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-24857 and fix it if it is affected.\n\nWhat it is: CVE-2022-24857 is a high-severity authentication bypass vulnerability in xi django-mfa3, published on 15 Apr 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-24857 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0\n- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0\n- django-mfa3 (PyPI): affected all versions; fixed in 0.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-24857/ (Markdown: https://insights.sbomify.com/CVE-2022-24857/index.md)","id":"CVE-2022-24857","markdown":"https://insights.sbomify.com/CVE-2022-24857/index.md","name":"CVE-2022-24857","record":{"aliases":["GHSA-3r7g-wrpr-j5g4","PYSEC-2022-192"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Django MFA library","requires_auth":"low_privilege","summary":"Attackers can bypass multi-factor authentication by accessing the unmodified Django admin login view, requiring users to upgrade the library or configure routes.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"django-mfa3","vendor":"django-mfa3_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. Users are affected if they have activated both django-mfa3 (\u003c 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. The issue has been fixed in django-mfa3 0.5.0. It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition *before* the admin routes: url('admin/login/', lambda request: redirect(settings.LOGIN_URL)","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Multi factor authentication bypass in django-mfa3","id":"CVE-2022-24857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":3,"n_references":4,"next":{"headline":"Default redirect callback vulnerable to open redirects","id":"CVE-2022-24858"},"packages":[{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"django-mfa3","purl":null,"source":"GHSA-3r7g-wrpr-j5g4"},{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"django-mfa3","purl":"pkg:pypi/django-mfa3","source":"GHSA-3r7g-wrpr-j5g4"},{"ecosystem":"PyPI","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"django-mfa3","purl":"pkg:pypi/django-mfa3","source":"PYSEC-2022-192"}],"prev":{"headline":"Server-Side Request Forgery in FlyteConsole","id":"CVE-2022-24856"},"products":["django-mfa3"],"published":"2022-04-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["xi"]},"summary":"Attackers can bypass multi-factor authentication by accessing the unmodified Django admin login view, requiring users to upgrade the library or configure routes.","url":"https://insights.sbomify.com/CVE-2022-24857/"}