CVE-2016-6582 — doorkeeper
CRITICALCVE-2016-6582 is a critical-severity (CVSS 9.1) CWE-254 vulnerability in doorkeeper. A fix is available for doorkeeper — see the affected versions and patch details below.
Doorkeeper is vulnerable to replay attacks
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
doorkeeperReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | doorkeeper | all versions | 4.2.0bundle update doorkeeper --conservative |
Affected Products
doorkeeperdoorkeeper_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doorkeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update doorkeeper to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6582 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2016-6582 in your dependencies?
Find it across RubyGems, including transitive dependencies.