Vulnerability in Doorkeeper Project
CVE-2016-6582
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.1 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.
EPSS exploit prediction
EPSS 0.048, 92.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- www.securityfocus.com/bid/92551 (Third Party Advisory, VDB Entry, vdb-entry)
- packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.html (VDB Entry, Third Party Advisory)
- 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, Patch, Mailing List, Third Party Advisory)
- github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0 (Patch, Third Party Advisory, Release Notes, Issue Tracking)
- github.com/doorkeeper-gem/doorkeeper/issues/875 (Patch, Third Party Advisory, Issue Tracking)