doorkeeper-openid_connect
Affected
- introduced
1.9.0, fixed1.10.0(ecosystem)
Fixed versions
1.10.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-44476
Doorkeeper Openid Connect: Dynamic Client Registration feature creates public clients with client_secret
Impact
The DynamicClientRegistrationController#register action hard-codes confidential: false when creating applications (dynamic_client_registration_controller.rb:18-25), yet the response includes a client_secret and advertises token_endpoint_auth_methods_supported: ["client_secret_basic", "client_secret_post"].
Because Doorkeeper's Application.by_uid_and_secret treats a blank/missing secret as valid for non-confidential (public) clients, an
attacker who knows only the client_id (which is public information) can authenticate as the dynamically-registered client at the token endpoint.
Note that Dynamic Client Registration is opt-in feature which is disabled by default so only projects that explicitly enabled it are affected.
Steps to Reproduce
Doorkeeper::Application has confidential: false
Doorkeeper::Application.by_uid_and_secret(client_id, nil) — itreturns the application (credentials bypass)
client_id (no client_secret) — the token endpoint issues an access token
without any secret verification
Patches
Patched in 1.10.0
Workarounds
Upgrade existing applications created with a Dynamic Client registration to have confidential: true
Medium Basis: The source's own band: MODERATE
1.9.0, fixed 1.10.0 (ecosystem)1.10.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0