Description
The Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging failure to implement the OAuth 2.0 Token Revocation specification.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | ruby-doorkeeper | 4.2.0-3 | — |
| Debian 13 | ruby-doorkeeper | 4.2.0-3 | — |
| Debian 12 | ruby-doorkeeper | 4.2.0-3 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 16.04 LTS | ruby-doorkeeper | 2.2.1-1ubuntu0.1~esm2 | USN-7394-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| RubyGems | doorkeeper | < 4.2.0 | 4.2.0 | GHSA-3m6r-39p3-jq25 |
Advisories 1
- USN-7394-1 ruby-doorkeeper vulnerabilities Ubuntu Security Notices (USN) · Jun 25, 2026
References
- 92551 vdb-entry
- http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.html
- 20160818 [CVE-2016-6582] Doorkeeper gem does not revoke tokens & uses wrong auth/auth method mailing-list
- 20160822 [CVE-2016-6582] Doorkeeper gem does not revoke tokens & uses wrong auth/auth method mailing-list
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0
- https://github.com/doorkeeper-gem/doorkeeper/issues/875