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
Configurations
History
21 Nov 2024, 02:56
Type | Values Removed | Values Added |
---|---|---|
References | () http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.html - Third Party Advisory, VDB Entry | |
References | () http://seclists.org/fulldisclosure/2016/Aug/105 - Mailing List, Patch, Third Party Advisory | |
References | () http://www.securityfocus.com/archive/1/539268/100/0/threaded - | |
References | () http://www.securityfocus.com/bid/92551 - Third Party Advisory, VDB Entry | |
References | () https://github.com/doorkeeper-gem/doorkeeper/issues/875 - Issue Tracking, Patch, Third Party Advisory | |
References | () https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0 - Issue Tracking, Patch, Release Notes, Third Party Advisory |
Information
Published : 2017-01-23 21:59
Updated : 2024-11-21 02:56
NVD link : CVE-2016-6582
Mitre link : CVE-2016-6582
CVE.ORG link : CVE-2016-6582
JSON object : View
Products Affected
doorkeeper_project
- doorkeeper
CWE
CWE-254
7PK - Security Features