Doorkeeper subject to Incorrect Permission Assignment

published 2018-07-13 8y ago modified 2026-06-17 4mo ago also GHSA-694m-jhr9-pf77 , EUVD-2018-0373

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can result in Access tokens are not revoked for public OAuth apps, leaking access until expiry.

Patch / fix

fixed in 1 distros 1 links 1

rubygems doorkeeper 4.4.0

ruby-doorkeeper Debian 14, Debian 13, Debian 12 4.4.2-1

debian advisories DEBIAN-CVE-2018-1000211

github.com/doorkeeper-gem/doorkeeper#1119 pull request

Is CVE-2018-1000211 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
rubygems	doorkeeper	>=4.2.0, <4.4.0	4.4.0

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource

References

github.com /doorkeeper-gem/doorkeeper/pull/1119
web, third-party-advisory
github.com /doorkeeper-gem/doorkeeper/issues/891
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000211
advisory
github.com /advisories/GHSA-694m-jhr9-pf77
advisory
github.com /doorkeeper-gem/doorkeeper
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.