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 doorkeeper-gem/doorkeeper#1589

Fix doorkeeper-gem/doorkeeper#1646

References

• GHSA-7w2c-w47h-789w
• https://nvd.nist.gov/vuln/detail/CVE-2023-34246
• doorkeeper-gem/doorkeeper#1589
• doorkeeper-gem/doorkeeper#1646
• https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v5.6.6
• https://www.rfc-editor.org/rfc/rfc8252#section-8.6
• https://github.com/rubysec/ruby-advisory-db/blob/master/gems/doorkeeper/CVE-2023-34246.yml
• https://lists.debian.org/debian-lts-announce/2023/07/msg00016.html