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.
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