Use of a Key Past its Expiration Date Affecting github.com/zitadel/zitadel/internal/query package, versions >=2.62.0 <2.63.9>=2.64.0-rc.1 <2.64.6>=2.65.0-rc.1 <2.65.7>=2.66.0-rc.1 <2.66.16>=2.67.0-rc.1 <2.67.13>=2.68.0-rc.1 <2.68.9>=2.69.0-rc.1 <2.69.9>=2.70.0-rc.1 <2.70.8>=2.71.0-rc.1 <2.71.6
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMZITADELZITADELINTERNALQUERY-9667385
- published6 Apr 2025
- disclosed31 Mar 2025
- creditBilly Bolton
Introduced: 31 Mar 2025
NewCVE-2025-31123 (opens in a new tab)How to fix?
Upgrade github.com/zitadel/zitadel/internal/query to version 2.63.9, 2.64.6, 2.65.7, 2.66.16, 2.67.13, 2.68.9, 2.69.9, 2.70.8, 2.71.6 or higher.
Overview
Affected versions of this package are vulnerable to Use of a Key Past its Expiration Date in the CreateOIDCJWTProfileClient() function, which doesn't sufficiently check token expiry times for Authorization Grants. An attacker can obtain valid access tokens by using an expired JWT key.