Zitadel Expired JWT Keys Usable for Authorization Grants
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.63.9, 2.64.6, 2.65.7, 2.66.16, 2.67.13, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to retrieve tokens. Specifically, ZITADEL fails to properly check the expiration date of the JWT key when used for Authorization Grants. This allows an attacker with an expired key to obtain valid access tokens. This vulnerability does not affect the use of JWT Profile for OAuth 2.0 Client Authentication on the Token and Introspection endpoints, which correctly reject expired keys. This vulnerability is fixed in 2.71.6, 2.70.8, 2.69.9, 2.68.9, 2.67.13, 2.66.16, 2.65.7, 2.64.6, and 2.63.9.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- zitadel zitadel
From 2.62.0 · fixed in 2.63.9; From 2.64.0-rc.1 · fixed in 2.64.6; From 2.65.0-rc.1 · fixed in 2.65.7; From 2.66.0-rc.1 · fixed in 2.66.16; From 2.67.0-rc.1 · fixed in 2.67.13; From 2.68.0-rc.1 · fixed in 2.68.9; From 2.69.0-rc.1 · fixed in 2.69.9; From 2.70.0-rc.1 · fixed in 2.70.8; From 2.71.0-rc.1 · fixed in 2.71.6