Doorkeeper is vulnerable to replay attacks
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-6582US | critical9.1 | — | ||
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 Re… | ||||
02
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.htmlWEB
- http://seclists.org/fulldisclosure/2016/Aug/105WEB
- http://www.openwall.com/lists/oss-security/2016/08/19/2WEB
- https://github.com/advisories/GHSA-3m6r-39p3-jq25ADVISORY
- https://github.com/doorkeeper-gem/doorkeeperWEB
- https://github.com/doorkeeper-gem/doorkeeper/issues/875WEB
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/doorkeeper/CVE-2016-6582.ymlWEB
scry
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