GitHub Advisoryadvisory · Go

GHSA-6rrr-78xp-5jp8 Zitadel RefreshToken invalidation vulnerability

MEDIUM Published 2023-01-11 Modified 2023-01-24 Official page ↗
Aliases
CVE-2023-22492
Ecosystem
Go
Packages
github.com/zitadel/zitadel
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
Weaknesses
CWE-613
Reviewed
2023-01-11

Affected packages

• Go github.com/zitadel/zitadel: >= 2.17.0, < 2.17.3 → fixed in 2.17.3 • Go github.com/zitadel/zitadel: >= 2.0.0, < 2.16.4 → fixed in 2.16.4

Description

Impact 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). Patches 2.x versions are fixed on >= 2.17.3 2.16.x versions are fixed on >= 2.16.4 ZITADEL recommends upgrading to the latest versions available in due course. Workarounds Ensure the RefreshTokenExpiration in the OIDC settings of your instance is set according to your security requirements. References https://zitadel.com/docs/guides/manage/console/instance-settings#oidc-token-lifetimes-and-expiration

Related

Weakness · not in database (1)

Alias · CVE (1)

  • CVE-2023-22492 ZITADEL is a combination of Auth0 and Keycloak. vulnerability

References