Roadiz OpenID Connect nonce generated but never validated — ID token replay attack
roadiz core-bundle-dev-app
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| roadiz/openid Packagist |
|
|
roadiz core-bundle-dev-app
| Product | Affected | Fixed in |
|---|---|---|
| roadiz/openid Packagist |
|
|
Roadiz is a polymorphic content management system based on a node system. Prior to versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18, the roadiz/openid package generates an OIDC nonce in OAuth2LinkGenerator::generate() and includes it in the authorization request sent to the identity provider, but never stores it and never validates it on the callback. The OpenIdJwtConfigurationFactory validation chain does not include a nonce constraint, and OpenIdAuthenticator::authenticate() never checks the nonce claim in the returned ID token against a stored value. This issue has been patched in versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18.
From the CVE record · GitHub_M
The roadiz/openid package sends a nonce in OIDC authorization requests but does not store it or validate the nonce in returned ID tokens. This leaves the OIDC callback unable to verify that an ID token matches its authorization request. The input does not specify attacker access requirements or whether user interaction is needed.
Teams running roadiz/openid versions >=2.7.0 <2.7.18, >=2.6.0 <2.6.31, >=2.5.0 <2.5.45, or <2.3.43 should check their installations.