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.
References
Link | Resource |
---|---|
http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.html | Third Party Advisory VDB Entry |
http://seclists.org/fulldisclosure/2016/Aug/105 | Mailing List Patch Third Party Advisory |
http://www.securityfocus.com/archive/1/539268/100/0/threaded | |
http://www.securityfocus.com/bid/92551 | Third Party Advisory VDB Entry |
https://github.com/doorkeeper-gem/doorkeeper/issues/875 | Issue Tracking Patch Third Party Advisory |
https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0 | Issue Tracking Patch Third Party Advisory Release Notes |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2017-01-23T21:00:00
Updated: 2018-10-09T18:57:01
Reserved: 2016-08-03T00:00:00
Link: CVE-2016-6582
JSON object: View
NVD Information
Status : Modified
Published: 2017-01-23T21:59:02.110
Modified: 2018-10-09T20:00:44.897
Link: CVE-2016-6582
JSON object: View
Redhat Information
No data.
CWE