CVE-2016-6582
Doorkeeper Project Doorkeeper vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Doorkeeper. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Doorkeeper Project Doorkeeper runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- seclists.org/fulldisclosure/2016/Aug/105 · Patch
- github.com/doorkeeper-gem/doorkeeper/issues/875 · Patch
- github.com/doorkeeper-gem/doorkeeper/releases/tag/v4.2.0 · Patch
- packetstormsecurity.com/files/138430/Doorkeeper-4.1.0-Token-Revocation.html · Third Party Advisory
- www.securityfocus.com/bid/92551 · Third Party Advisory
- www.securityfocus.com/archive/1/539268/100/0/threaded
- nvd.nist.gov/vuln/detail/CVE-2016-6582
- cve.org/CVERecord?id=CVE-2016-6582
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.