doorkeeper-openid_connect is vulnerable to Improper Authorization
48
Medium Risk
The Dynamic Client Registration endpoint's DynamicClientRegistrationController#application_params assigns scopes directly from params[:scope] without checking it against Doorkeeper.configuration.scopes. With enforce_configured_scopes off (the default) and no authorize_dynamic_client_registration callback configured, a self registered client can request a scope such as admin that the server never intended to grant, and Doorkeeper's ScopeChecker checks the request against the client's own scopes rather than the server's configured set, so the client can reach the consent screen with privileges beyond what the server intended for dynamically registered clients. The fix persists only registration.permitted_scopes, the intersection with the server's configured default_scopes/optional_scopes, and rejects the registration with invalid_client_metadata when none of the requested scopes are supported.
You are affected if you are using a version that falls within the vulnerable range and you have Dynamic Client Registration enabled without enforce_configured_scopes turned on.
doorkeeper-openid_connect is vulnerable to Improper Authorization in versions 0.0.1 - 1.10.3.
Upgrade the doorkeeper-openid_connect library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.