CVE-2024-24771
Open Forms Multi-Factor Authentication Bypass Vulnerability
Description
Open Forms allows users create and publish smart forms. Versions prior to 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain a non-exploitable multi-factor authentication weakness. Superusers who have their credentials (username + password) compromised could potentially have the second-factor authentication bypassed if an attacker somehow managed to authenticate to Open Forms. The maintainers of Open Forms do not believe it is or has been possible to perform this login. However, if this were possible, the victim's account may be abused to view (potentially sensitive) submission data or have been used to impersonate other staff accounts to view and/or modify data. Three mitigating factors to help prevent exploitation include: the usual login page (at `/admin/login/`) does not fully log in the user until the second factor was succesfully provided; the additional non-MFA protected login page at `/api/v2/api-authlogin/` was misconfigured and could not be used to log in; and there are no additional ways to log in. This also requires credentials of a superuser to be compromised to be exploitable. Versions 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain the following patches to address these weaknesses: Move and only enable the API auth endpoints (`/api/v2/api-auth/login/`) with `settings.DEBUG = True`. `settings.DEBUG = True` is insecure and should never be applied in production settings. Additionally, apply a custom permission check to the hijack flow to only allow second-factor-verified superusers to perform user hijacking.
INFO
Published Date :
Feb. 7, 2024, 3:15 p.m.
Last Modified :
Feb. 15, 2024, 5:01 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.8
Exploitability Score :
1.3
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-24771.
| URL | Resource |
|---|---|
| https://github.com/open-formulieren/open-forms/releases/tag/2.2.9 | Release Notes |
| https://github.com/open-formulieren/open-forms/releases/tag/2.3.7 | Release Notes |
| https://github.com/open-formulieren/open-forms/releases/tag/2.4.5 | Release Notes |
| https://github.com/open-formulieren/open-forms/releases/tag/2.5.2 | Release Notes |
| https://github.com/open-formulieren/open-forms/security/advisories/GHSA-64r3-x3gf-vp63 | Mitigation Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-24771 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-24771 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Feb. 15, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N Changed Reference Type https://github.com/open-formulieren/open-forms/releases/tag/2.2.9 No Types Assigned https://github.com/open-formulieren/open-forms/releases/tag/2.2.9 Release Notes Changed Reference Type https://github.com/open-formulieren/open-forms/releases/tag/2.3.7 No Types Assigned https://github.com/open-formulieren/open-forms/releases/tag/2.3.7 Release Notes Changed Reference Type https://github.com/open-formulieren/open-forms/releases/tag/2.4.5 No Types Assigned https://github.com/open-formulieren/open-forms/releases/tag/2.4.5 Release Notes Changed Reference Type https://github.com/open-formulieren/open-forms/releases/tag/2.5.2 No Types Assigned https://github.com/open-formulieren/open-forms/releases/tag/2.5.2 Release Notes Changed Reference Type https://github.com/open-formulieren/open-forms/security/advisories/GHSA-64r3-x3gf-vp63 No Types Assigned https://github.com/open-formulieren/open-forms/security/advisories/GHSA-64r3-x3gf-vp63 Mitigation, Vendor Advisory Added CPE Configuration OR *cpe:2.3:a:maykinmedia:open_forms:*:*:*:*:*:*:*:* versions up to (excluding) 2.2.9 *cpe:2.3:a:maykinmedia:open_forms:*:*:*:*:*:*:*:* versions from (including) 2.3.0 up to (excluding) 2.3.7 *cpe:2.3:a:maykinmedia:open_forms:*:*:*:*:*:*:*:* versions from (including) 2.4.0 up to (excluding) 2.4.5 *cpe:2.3:a:maykinmedia:open_forms:*:*:*:*:*:*:*:* versions from (including) 2.5.0 up to (excluding) 2.5.2 -
CVE Received by [email protected]
Feb. 07, 2024
Action Type Old Value New Value Added Description Open Forms allows users create and publish smart forms. Versions prior to 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain a non-exploitable multi-factor authentication weakness. Superusers who have their credentials (username + password) compromised could potentially have the second-factor authentication bypassed if an attacker somehow managed to authenticate to Open Forms. The maintainers of Open Forms do not believe it is or has been possible to perform this login. However, if this were possible, the victim's account may be abused to view (potentially sensitive) submission data or have been used to impersonate other staff accounts to view and/or modify data. Three mitigating factors to help prevent exploitation include: the usual login page (at `/admin/login/`) does not fully log in the user until the second factor was succesfully provided; the additional non-MFA protected login page at `/api/v2/api-authlogin/` was misconfigured and could not be used to log in; and there are no additional ways to log in. This also requires credentials of a superuser to be compromised to be exploitable. Versions 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain the following patches to address these weaknesses: Move and only enable the API auth endpoints (`/api/v2/api-auth/login/`) with `settings.DEBUG = True`. `settings.DEBUG = True` is insecure and should never be applied in production settings. Additionally, apply a custom permission check to the hijack flow to only allow second-factor-verified superusers to perform user hijacking. Added Reference GitHub, Inc. https://github.com/open-formulieren/open-forms/security/advisories/GHSA-64r3-x3gf-vp63 [No types assigned] Added Reference GitHub, Inc. https://github.com/open-formulieren/open-forms/releases/tag/2.2.9 [No types assigned] Added Reference GitHub, Inc. https://github.com/open-formulieren/open-forms/releases/tag/2.3.7 [No types assigned] Added Reference GitHub, Inc. https://github.com/open-formulieren/open-forms/releases/tag/2.4.5 [No types assigned] Added Reference GitHub, Inc. https://github.com/open-formulieren/open-forms/releases/tag/2.5.2 [No types assigned] Added CWE GitHub, Inc. CWE-287 Added CWE GitHub, Inc. CWE-284 Added CWE GitHub, Inc. CWE-654 Added CVSS V3.1 GitHub, Inc. AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-24771 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-24771
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.08 }} 0.03%
score
0.30395
percentile