Doorkeeper OpenID Connect: DCR endpoint persists unvalidated client-supplied scopes
doorkeeper-gem doorkeeper-openid_connect
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| doorkeeper-gem doorkeeper-openid_connect |
| No fix yet |
Original description
Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client Registration (DCR) endpoint persists client-supplied scopes without validating them against the server's configured scope set. Under certain conditions, this allows a self-registered client to obtain scopes beyond what the server intended to grant. In DynamicClientRegistrationController#application_params, the scopes attribute is assigned directly from params[:scope] with no validation against Doorkeeper.configuration.scopes or optional_scopes. Combined with enforce_configured_scopes being off by default and Doorkeeper's ScopeChecker prioritizing application-level scopes over server-level scopes, this creates a privilege escalation path. This issue is fixed in version 1.10.4.
From the CVE record · GitHub_M