Improper Authentication in Doorkeeper - #VU159530
Published: November 6, 2026 / Updated: November 6, 2026
Vulnerability details
The vulnerability allows an unauthenticated network attacker to enumerate applications holding active machine-to-machine tokens, revoke their access tokens and grants to deny service to dependent integrations, and access application-management screens exposing client identifiers and, when secrets are stored in plaintext, client secrets.
The vulnerability exists due to Doorkeeper authentication helpers ignoring authenticator return values without halting requests: when authorized-applications routes are mounted and ownerless tokens exist, Doorkeeper::AuthorizedApplicationsController proceeds with a nil resource owner if resource_owner_authenticator is absent and uses its nil-returning default or a custom block returns nil without halting, causing resource-owner queries to select all records with a NULL owner, including under polymorphic_resource_owner, while Doorkeeper::ApplicationsController similarly leaves application-management screens accessible when admin_authenticator returns nil without halting, including from an empty block. An unauthenticated network attacker can send GET requests to /oauth/authorized_applications to obtain application identifiers, names, and creation timestamps and DELETE requests to /oauth/authorized_applications/:id to revoke each application's active client_credentials tokens and grants without credentials, a session, or user interaction, disrupting integrations until new tokens are obtained and controlling when revocation-related logs or alerts fire where configured, with cross-site requests also possible in api_only mode because these routes lack CSRF protection, or access application-management screens under the separate nil-returning administrator-authenticator condition.