CVE-2016-6582
UnknownEPSS 4.69%
Last modified
CVE-2016-6582 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 4.69% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Doorkeeper Project | Doorkeeper | <= 4.1.0 |
References
- http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.htmlThird Party Advisory, VDB Entry
- http://seclists.org/fulldisclosure/2016/Aug/105Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/92551Third Party Advisory, VDB Entry
- https://github.com/doorkeeper-gem/doorkeeper/issues/875Issue Tracking, Patch, Third Party Advisory
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0Issue Tracking, Patch, Release Notes, Third Party Advisory
- http://packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.htmlThird Party Advisory, VDB Entry
- http://seclists.org/fulldisclosure/2016/Aug/105Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/92551Third Party Advisory, VDB Entry
- https://github.com/doorkeeper-gem/doorkeeper/issues/875Issue Tracking, Patch, Third Party Advisory
- https://github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0Issue Tracking, Patch, Release Notes, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is 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.
How severe is CVE-2016-6582?
Severity scoring for CVE-2016-6582 is pending analysis. The EPSS model estimates a 4.69% probability of exploitation in the next 30 days.
How do I fix CVE-2016-6582?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-6566The valueAsString parameter inside the JSON payload containe…
- CVE-2016-6567SHDesigns' Resident Download Manager provides firmware updat…
- CVE-2016-6578CodeLathe FileCloud, version 13.0.0.32841 and earlier, conta…8.8
- CVE-2016-6579Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-6580A HTTP/2 implementation built using any version of the Pytho…
- CVE-2016-6581A HTTP/2 implementation built using any version of the Pytho…
- CVE-2016-6585A Denial of Service vulnerability exists in Symantec Norton …5.3
- CVE-2016-6586A security bypass vulnerability exists in Symantec Norton Mo…3.7
- CVE-2016-6587An Information Disclosure vulnerability exists in the mid.da…5.5
- CVE-2016-6588A Cross-Site Scripting (XSS) vulnerability exists in the ITM…5.4
- CVE-2016-6589A Denial of Service vulnerability exists in the ITMS workflo…6.5
- CVE-2016-6590A privilege escalation vulnerability exists when loading DLL…7.8
Are you affected by CVE-2016-6582?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST