RefreshToken invalidation vulnerability
cve-program · CVE-2023-22492
PublishedZITADEL 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.
Read the publisher's advisoryeuvd · EUVD-2023-0370
PublishedZITADEL 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.
Read the publisher's advisorynvd · CVE-2023-22492
PublishedZITADEL 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.
Read the publisher's advisoryosv · GHSA-6rrr-78xp-5jp8
Published### 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](https://github.com/zitadel/zitadel/releases/tag/v2.17.3) 2.16.x versions are fixed on >= [2.16.4](https://github.com/zitadel/zitadel/releases/tag/v2.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
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2023-22492 · CVE overview and exploitation status
cve-program · CVE-2023-22492
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2
euvd · EUVD-2023-0370
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2
nvd · CVE-2023-22492
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8
osv · GHSA-6rrr-78xp-5jp8
- https://github.com/zitadel/zitadel/security/advisories/GHSA-6rrr-78xp-5jp8
- https://nvd.nist.gov/vuln/detail/CVE-2023-22492
- https://github.com/zitadel/zitadel/commit/301e22c4956ead6014a8179463c37263f7301a83
- https://github.com/zitadel/zitadel/commit/fc892c52a10cd4ffdac395747494f3a93a7494c2
- https://github.com/zitadel/zitadel
- https://github.com/zitadel/zitadel/releases/tag/v2.16.4
- https://github.com/zitadel/zitadel/releases/tag/v2.17.3
Related changes
Linked by CVE identifierNo related changes are available here.