CVEvulnerability
CVE-2023-22492
5.9 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2023-01-11
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
- CVSS 3.1 ([email protected])
- 5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- CWE-613
Description
ZITADEL is a combination of Auth0 and Keycloak. RefreshTokens is an OAuth 2.0 feature that allows applications to retrieve new access tokens and refresh the user's session without the need for interacting with a UI. RefreshTokens were not invalidated when a user was locked or deactivated. The deactivated or locked user was able to obtain a valid access token only through a refresh token grant. When the locked or deactivated user’s session was already terminated (“logged out”) then it was not possible to create a new session. Renewal of access token through a refresh token grant is limited to the configured amount of time (RefreshTokenExpiration). As a workaround, ensure the RefreshTokenExpiration in the OIDC settings of your instance is set according to your security requirements. This issue has been patched in versions 2.17.3 and 2.16.4.
Affected configurations
• zitadel zitadel (>= 2.0.0 < 2.16.4)
• zitadel zitadel (>= 2.17.0 < 2.17.3)
Related
Weakness · not in database (1)
References
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83 Patch, Third Party Advisory
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2 Patch, Third Party Advisory
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8 Patch, Third Party Advisory
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83 Patch, Third Party Advisory
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2 Patch, Third Party Advisory
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8 Patch, Third Party Advisory