HighGHSA-j7vx-8mqj-cqp9CVE-2020-10187

Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper

Published 7 May 2020 · Updated 10 Sept 2026

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 packages

doorkeeperRubyGems
Affected
>=5.0.0 <5.0.3
Fixed in
5.0.3
Update to the fixed version for your release line, for example:bundle update --conservative doorkeeper # Gemfile: '>= 5.0.3'
doorkeeperRubyGems
Affected
>=5.1.0 <5.1.1
Fixed in
5.1.1
Update to the fixed version for your release line, for example:bundle update --conservative doorkeeper # Gemfile: '>= 5.1.1'
doorkeeperRubyGems
Affected
>=5.2.0 <5.2.5
Fixed in
5.2.5
Update to the fixed version for your release line, for example:bundle update --conservative doorkeeper # Gemfile: '>= 5.2.5'
doorkeeperRubyGems
Affected
>=5.3.0 <5.3.2
Fixed in
5.3.2
Update to the fixed version for your release line, for example:bundle update --conservative doorkeeper # Gemfile: '>= 5.3.2'

Details

Impact

Information disclosure vulnerability. Allows an attacker to see all Doorkeeper::Application model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).

Patches

These versions have the fix:

  • 5.0.3
  • 5.1.1
  • 5.2.5
  • 5.3.2

Workarounds

Patch Doorkeeper::Application model #as_json(options = {}) method and define only those attributes you want to expose.

Additional recommended hardening is to enable application secrets hashing (guide), available since Doorkeeper 5.1. This would render the exposed secret useless.

References

  • Commit with fix: https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10187

Is GHSA-j7vx-8mqj-cqp9 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
  • MediumCVE-2014-8144Doorkeeper vulnerable to Cross-site Request Forgery · 17 Sept 2018
  • HighCVE-2018-1000211Doorkeeper subject to Incorrect Permission Assignment · 13 Aug 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.