CVE-2023-22492

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

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).

CVE-2023-22492 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.17.3, 2.16.4); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2023-22492? CVE-2023-22492 is a medium-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 2.17.0, < 2.17.3. It is fixed in 2.17.3, 2.16.4.
2. How severe is CVE-2023-22492? CVE-2023-22492 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/zitadel/zitadel are affected by CVE-2023-22492? github.com/zitadel/zitadel (go) versions >= 2.17.0, < 2.17.3 is affected.
4. Is there a fix for CVE-2023-22492? Yes. CVE-2023-22492 is fixed in 2.17.3, 2.16.4. Upgrade to this version or later.
5. Is CVE-2023-22492 exploitable, and should I be worried? Whether CVE-2023-22492 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-22492 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-22492?
   • Upgrade github.com/zitadel/zitadel to 2.17.3 or later
   • Upgrade github.com/zitadel/zitadel to 2.16.4 or later