Doorkeeper: When using public clients, any client can revoke any access token
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| doorkeeper-gem | doorkeeper | affected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to 5.9.1, Doorkeeper's OAuth token revocation flow does not correctly authorize revocation requests when public, non-confidential clients are used, allowing tokens to be revoked without correct authorization. This issue is fixed in version 5.9.1. | |
| Title | Doorkeeper: When using public clients, any client can revoke any access token | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|
No data.
Improper Authorization
No data.
No data.
No data.
No data.