Doorkeeper Improper Authentication vulnerability
OAuth RFC 8252 says https://www.rfc-editor.org/rfc/rfc8252#section-8.6 > the authorization server SHOULD NOT process authorization requests automatically without user consent or interaction, except when the identity of the client can be assured. **This includes the case where the user has previously approved an authorization request for a given client id** But Doorkeeper automatically processes authorization requests without user consent for public clients that have been previously approved. Public clients are inherently vulnerable to impersonation, their identity cannot be assured. Issue https://github.com/doorkeeper-gem/doorkeeper/issues/1589 Fix https://github.com/doorkeeper-gem/doorkeeper/pull/1646
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-34246US | medium6.5 | — | ||
Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to version 5.6.6, Doorkeeper automatically processes authorization requests without user consent for public clien… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/doorkeeper-gem/doorkeeperPACKAGE
- https://github.com/doorkeeper-gem/doorkeeper/issues/1589WEB
- https://github.com/doorkeeper-gem/doorkeeper/pull/1646WEB
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v5.6.6WEB
- https://github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-7w2c-w47h-789wWEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/doorkeeper/CVE-2023-34246.ymlWEB
- https://lists.debian.org/debian-lts-announce/2023/07/msg00016.htmlWEB
- https://lists.debian.org/debian-lts-announce/2024/12/msg00010.htmlWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan