What is CVE-2022-24857?

CVE-2022-24857 is a high-severity improper authentication vulnerability in django-mfa3 (pip), affecting versions < 0.5.0. It is fixed in 0.5.0. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2022-24857?

CVE-2022-24857 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of django-mfa3 are affected by CVE-2022-24857?

django-mfa3 (pip) versions < 0.5.0 is affected.

Is there a fix for CVE-2022-24857?

Yes. CVE-2022-24857 is fixed in 0.5.0. Upgrade to this version or later.

Is CVE-2022-24857 exploitable, and should I be worried?

Whether CVE-2022-24857 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-24857 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-24857?

Upgrade django-mfa3 to 0.5.0 or later.

CVE-2022-24857 in django-mfa3

Q: How severe is CVE-2022-24857?

CVE-2022-24857 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of django-mfa3 are affected by CVE-2022-24857?

django-mfa3 (pip) versions < 0.5.0 is affected.

Q: Is there a fix for CVE-2022-24857?

Yes. CVE-2022-24857 is fixed in 0.5.0. Upgrade to this version or later.

Q: Is CVE-2022-24857 exploitable, and should I be worried?

Whether CVE-2022-24857 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-24857 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-24857?

Upgrade django-mfa3 to 0.5.0 or later.

Summary

Improper Authentication in django-mfa3

Workarounds

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)

References

django-mfa3 changelog

Impact

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.

You are affected if you have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2022-24857 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.5.0); upgrading removes the vulnerable code path.

Affected versions

django-mfa3 (< 0.5.0)

Security releases

django-mfa3 → 0.5.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been fixed in django-mfa3 0.5.0.

Frequently Asked Questions

What is CVE-2022-24857? CVE-2022-24857 is a high-severity improper authentication vulnerability in django-mfa3 (pip), affecting versions < 0.5.0. It is fixed in 0.5.0. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2022-24857? CVE-2022-24857 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of django-mfa3 are affected by CVE-2022-24857? django-mfa3 (pip) versions < 0.5.0 is affected.
Is there a fix for CVE-2022-24857? Yes. CVE-2022-24857 is fixed in 0.5.0. Upgrade to this version or later.
Is CVE-2022-24857 exploitable, and should I be worried? Whether CVE-2022-24857 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-24857 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-24857? Upgrade django-mfa3 to 0.5.0 or later.