HighGHSA-694m-jhr9-pf77CVE-2018-1000211

Doorkeeper subject to Incorrect Permission Assignment

Published 13 Aug 2018 · Updated 8 Nov 2023

Is your project on an affected doorkeeper?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

doorkeeperRubyGems
Affected
>=4.2.0 <4.4.0
Fixed in
4.4.0
Update to the fixed version for your release line, for example:bundle update --conservative doorkeeper # Gemfile: '>= 4.4.0'

Details

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.

Is GHSA-694m-jhr9-pf77 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected doorkeeper, and gives you the command that fixes it.

More advisories for doorkeeper

  • MediumCVE-2026-115472Doorkeeper: When using public clients, any client can revoke any access token · 19 Nov 2026
  • MediumCVE-2023-34246Doorkeeper Improper Authentication vulnerability · 12 Jun 2023
  • HighCVE-2020-10187Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper · 7 May 2020
  • MediumCVE-2014-8144Doorkeeper vulnerable to Cross-site Request Forgery · 17 Sept 2018
  • MediumCVE-2018-1000088Doorkeeper is vulnerable to stored XSS and code execution · 13 Mar 2018
  • CriticalCVE-2016-6582Doorkeeper is vulnerable to replay attacks · 24 Oct 2017
doorkeeper security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.