CVE-2022-31145

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.

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.

Improper validation of access tokens can permit use of expired tokens.

### Impact Authenticated users using an external identity provider can continue to use Access Tokens and ID Tokens even after they expire. Using flyteadmin as the OAuth2 Authorization Server is unaffected by this issue. ### Patches 1.1.30 ### Workarounds Rotating signing keys immediately will: * Invalidate all open sessions, * Force all users to attempt to obtain new tokens. Continue to rotate keys until flyteadmin has been upgraded, Hide flyteadmin deployment ingress url from the internet. ### References https://github.com/flyteorg/flyteadmin/pull/455 ### For more information If you have any questions or comments about this advisory: * Open an issue in [flyte repo](https://github.com/flyteorg/flyte/issues) * Email us at [flyte](mailto:admin@flyte.org)

FlyteAdmin es el plano de control de Flyte responsable de la administración de entidades y de la administración de las ejecuciones del flujo de trabajo. En versiones 1.1.30 y anteriores, los usuarios autenticados usando un proveedor de identidad externo pueden seguir usando los tokens de acceso y los tokens de identificación incluso después de que expiren. Los usuarios que usan FlyteAdmin como servidor de autorización OAuth2 no están afectados por este problema. Se presenta un parche disponible en la rama "master" del repositorio. Como mitigación, rotar las claves de firma inmediatamente invalidará todas las sesiones abiertas y obligará a todos los usuarios a intentar obtener nuevos tokens. Aquellos que usen esta mitigación deberían continuar rotando las claves hasta que FlyteAdmin haya sido actualizado y ocultar la URL de entrada del despliegue de FlyteAdmin de Internet