Skip to content

Zitadel RefreshToken invalidation vulnerability

Moderate severity GitHub Reviewed Published Jan 11, 2023 in zitadel/zitadel • Updated Jan 24, 2023

Package

gomod github.com/zitadel/zitadel (Go)

Affected versions

>= 2.17.0, < 2.17.3
>= 2.0.0, < 2.16.4

Patched versions

2.17.3
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

References

@livio-a livio-a published to zitadel/zitadel Jan 11, 2023
Published to the GitHub Advisory Database Jan 11, 2023
Reviewed Jan 11, 2023
Published by the National Vulnerability Database Jan 11, 2023
Last updated Jan 24, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N

EPSS score

0.114%
(46th percentile)

Weaknesses

CVE ID

CVE-2023-22492

GHSA ID

GHSA-6rrr-78xp-5jp8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.