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: 2017-01-23 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-6582 is rated Moderate Risk (63.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.01%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-6582

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.64% 1.01% +0.37%
2 2026-05-09 1.59% 0.64% -0.95%
3 2025-09-15 — 1.59% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-6582

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.2 [email protected]
6.4 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 4.9 [email protected]

Weakness enumeration for CVE-2016-6582

GitHub Security Advisory for CVE-2016-6582

GHSA-3m6r-39p3-jq25 · Severity: critical · Ecosystem: rubygems — Doorkeeper is vulnerable to replay attacks

OS Trackers for CVE-2016-6582

vendor priority summary link
debian not yet assigned CVE-2016-6582 not yet assigned priority: Debian including 1 source packages (ruby-doorkeeper), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-6582
ubuntu medium CVE-2016-6582 medium priority: Ubuntu including 1 source packages (ruby-doorkeeper), 21 status rows across 21 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, precise, trusty, upstream, xenial, yakkety, zesty): not-affected 17, DNE 2, released 2. https://ubuntu.com/security/CVE-2016-6582

Affected software / configurations for CVE-2016-6582

Vendor Product Version Raw CPE
doorkeeper_project doorkeeper <= 4.1.0 cpe:2.3:a:doorkeeper_project:doorkeeper:*:*:*:*:*:ruby:*:*

References for CVE-2016-6582

cvelogic Threat Intelligence