CVE-2018-1000211

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.

Published: 2018-07-13 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1000211 is rated Moderate Risk (46.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.28%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1000211

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-30 0.89% 0.28% -0.61%
2 2025-03-29 0.30% 0.89% +0.59%
3 2025-03-17 — 0.30% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1000211

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2018-1000211

GitHub Security Advisory for CVE-2018-1000211

GHSA-694m-jhr9-pf77 · Severity: high · Ecosystem: rubygems — Doorkeeper subject to Incorrect Permission Assignment

OS Trackers for CVE-2018-1000211

vendor priority summary link
debian not yet assigned CVE-2018-1000211 not yet assigned priority: Debian including 1 source packages (ruby-doorkeeper), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2018-1000211
ubuntu medium CVE-2018-1000211 medium priority: Ubuntu including 1 source packages (ruby-doorkeeper), 18 status rows across 18 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): not-affected 13, ignored 3, DNE 1, released 1. https://ubuntu.com/security/CVE-2018-1000211

Affected software / configurations for CVE-2018-1000211

Vendor Product Version Raw CPE
doorkeeper_project doorkeeper <= 4.2.0 cpe:2.3:a:doorkeeper_project:doorkeeper:*:*:*:*:*:*:*:*

References for CVE-2018-1000211

cvelogic Threat Intelligence