Skip to main content

CVE-2022-46145: CWE-287: Improper Authentication in goauthentik authentik

Medium
Published: Fri Dec 02 2022 (12/02/2022, 17:12:42 UTC)
Source: CVE
Vendor/Project: goauthentik
Product: authentik

Description

authentik is an open-source identity provider. Versions prior to 2022.11.2 and 2022.10.2 are vulnerable to unauthorized user creation and potential account takeover. With the default flows, unauthenticated users can create new accounts in authentik. If a flow exists that allows for email-verified password recovery, this can be used to overwrite the email address of admin accounts and take over their accounts. authentik 2022.11.2 and 2022.10.2 fix this issue. As a workaround, a policy can be created and bound to the `default-user-settings-flow flow` with the contents `return request.user.is_authenticated`.

AI-Powered Analysis

AILast updated: 06/22/2025, 11:21:44 UTC

Technical Analysis

CVE-2022-46145 is a vulnerability classified under CWE-287 (Improper Authentication) affecting the open-source identity provider software authentik, specifically versions prior to 2022.10.2 and between 2022.11.0 and 2022.11.2. authentik is designed to manage user identities and authentication flows for organizations. The vulnerability arises from the default user creation flows that allow unauthenticated users to create new accounts without proper verification. This flaw enables attackers to register new accounts without authentication, which in itself is a security risk. More critically, if the deployment includes a flow that permits email-verified password recovery, attackers can exploit this mechanism to overwrite the email addresses associated with administrator accounts. By doing so, they can effectively take over these privileged accounts, gaining unauthorized administrative access to the authentik system. This can lead to full compromise of identity management functions, potentially allowing attackers to manipulate authentication policies, user permissions, and access controls across connected systems. The issue was addressed in authentik versions 2022.10.2 and 2022.11.2 by fixing the authentication checks in user creation flows. As an interim mitigation, administrators can create and bind a policy to the 'default-user-settings-flow' that enforces the condition 'return request.user.is_authenticated', effectively preventing unauthenticated user creation. There are no known exploits in the wild reported to date, but the vulnerability's nature makes it a significant risk if left unpatched, especially in environments where authentik is used as a critical identity provider.

Potential Impact

For European organizations, the impact of this vulnerability can be substantial. Identity providers like authentik are central to managing user authentication and authorization across enterprise applications and services. Unauthorized creation of user accounts and potential takeover of administrator accounts can lead to severe breaches of confidentiality, integrity, and availability. Attackers gaining admin access could manipulate user permissions, access sensitive data, disrupt authentication services, or pivot to other internal systems. This could result in data breaches, operational disruptions, and compliance violations under regulations such as GDPR. Organizations relying on authentik for single sign-on (SSO) or multi-factor authentication (MFA) could see these security controls undermined, increasing the risk of lateral movement by attackers. The vulnerability's exploitation does not require prior authentication, lowering the barrier for attackers. Given the critical role of identity providers, the threat extends beyond individual organizations to potentially impact supply chains and partner ecosystems within Europe.

Mitigation Recommendations

Beyond applying the official patches in authentik versions 2022.10.2 or 2022.11.2, European organizations should take the following specific steps: 1) Immediately implement the recommended policy binding to the 'default-user-settings-flow' to enforce authentication on user creation flows, preventing unauthenticated account creation. 2) Audit existing user accounts, especially administrator accounts, for unauthorized changes to email addresses or other credentials, and reset passwords where suspicious activity is detected. 3) Review and restrict password recovery flows to ensure they require strong verification and cannot be abused to overwrite critical account information. 4) Monitor authentik logs for unusual account creation patterns or password recovery requests originating from unknown or suspicious IP addresses. 5) Employ network segmentation and access controls to limit exposure of the authentik service to trusted networks and users only. 6) Educate administrators and security teams about this vulnerability and ensure rapid incident response capabilities are in place. 7) Consider integrating additional identity verification steps or MFA for administrative account changes to reduce risk of takeover. 8) Regularly update authentik and related identity infrastructure components to incorporate security fixes and improvements.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2022-11-28T17:27:19.995Z
Cisa Enriched
true

Threat ID: 682d9846c4522896dcbf4ebc

Added to database: 5/21/2025, 9:09:26 AM

Last enriched: 6/22/2025, 11:21:44 AM

Last updated: 8/18/2025, 11:28:48 PM

Views: 13

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats