LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000211: Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation AP...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Doorkeeper’s token revocation path may fail for public OAuth applications. A user or system can believe an access token was revoked, while the token actually remains usable until its normal expiry. Business urgency depends on how many public OAuth clients exist and how long access tokens remain valid.

Executive priority

Treat as a targeted OAuth control weakness, not a broad remote compromise signal. Prioritize if public OAuth clients protect sensitive data, tokens are long-lived, or revocation is part of incident response or account disconnect workflows.

Technical view

CVE-2018-1000211 describes incorrect access control in Doorkeeper 4.2.0 and later, specifically the token revocation API authorized method. The stated result is that access tokens are not revoked for public OAuth apps, leaving access active until expiry. The source bundle does not provide CVSS, CWE, fixed version, or affected CPE data.

Likely exposure

Exposure is most likely in Ruby applications using Doorkeeper 4.2.0 or later with public OAuth clients and relying on token revocation for logout, consent withdrawal, incident response, or account disconnect flows.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. The practical risk is failed revocation: access expected to be removed may persist until token expiry, especially where token lifetimes are long.

Researcher notes

Evidence is limited to the CVE description and GitHub issue/pull-request references. The bundle does not name a fixed release, CVSS vector, CWE, exploit activity, or exact affected package range beyond Doorkeeper 4.2.0 and later.

Mitigation direction

  • Check vendor issue and pull request guidance for fixed release details.
  • Inventory applications using Doorkeeper 4.2.0 or later.
  • Prioritize systems with public OAuth clients and sensitive scopes.
  • Upgrade Doorkeeper when the vendor-confirmed fixed version is identified.
  • Reduce reliance on revocation assumptions until behavior is validated.

Validation and detection

  • Identify public OAuth clients configured in Doorkeeper-backed applications.
  • Confirm whether token revocation works for public clients in a safe test environment.
  • Review token lifetimes for affected applications.
  • Check logs for failed or ineffective revocation attempts.
  • Verify remediation by confirming revoked tokens no longer grant access.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1000211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.