Learn about CVE-2022-31145 affecting FlyteAdmin versions <= 1.1.30. Understand the impact, technical details, and mitigation steps for this security vulnerability.
FlyteAdmin is the control plane for Flyte responsible for managing entities and administering workflow executions. In versions 1.1.30 and prior, authenticated users using an external identity provider can continue to use Access Tokens and ID Tokens even after they expire. Users who use FlyteAdmin as the OAuth2 Authorization Server are unaffected by this issue. A patch is available on the
master
branch of the repository. As a workaround, rotating signing keys immediately will invalidate all open sessions and force all users to attempt to obtain new tokens. Those who use this workaround should continue to rotate keys until FlyteAdmin has been upgraded and hide FlyteAdmin deployment ingress URL from the internet.
Understanding CVE-2022-31145
This CVE refers to an issue in FlyteAdmin versions 1.1.30 and earlier that allows authenticated users using an external identity provider to continue using Access Tokens and ID Tokens after their expiration.
What is CVE-2022-31145?
CVE-2022-31145 highlights the lack of proper validation for Access Tokens and ID Tokens in FlyteAdmin versions 1.1.30 and prior, potentially leading to a security risk for affected users.
The Impact of CVE-2022-31145
The vulnerability can impact the integrity of the system as authenticated users can still utilize expired Access Tokens and ID Tokens, posing a risk of unauthorized access or misuse of privileges.
Technical Details of CVE-2022-31145
In FlyteAdmin versions 1.1.30 and prior, the issue arises from insufficient expiration checks on Access Tokens and ID Tokens, allowing continued usage post-expiration.
Vulnerability Description
The vulnerability lies in the validation mechanism of Access Tokens and ID Tokens, permitting users to operate with expired tokens, compromising system security.
Affected Systems and Versions
FlyteAdmin versions <= 1.1.30 are impacted by this vulnerability, while users who use FlyteAdmin as the OAuth2 Authorization Server remain unaffected.
Exploitation Mechanism
Authenticated users leveraging an external identity provider can exploit this issue by continuing to use expired Access Tokens and ID Tokens.
Mitigation and Prevention
To address CVE-2022-31145, immediate steps are necessary to enhance security measures.
Immediate Steps to Take
Users are advised to apply the available patch on the
master
branch of the repository to mitigate the vulnerability. Additionally, rotating signing keys is recommended to invalidate open sessions and prompt users to acquire new tokens.
Long-Term Security Practices
It is crucial to regularly update and patch FlyteAdmin to the latest version to prevent security vulnerabilities like CVE-2022-31145. Furthermore, hiding FlyteAdmin deployment ingress URL from the internet is a precautionary measure to enhance security.
Patching and Updates
Ensuring prompt installation of security patches and updates for FlyteAdmin is essential in safeguarding systems against potential security risks.