Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper (CVE-2020-10187)

Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper (CVE-2020-10187) | HOL Guard CVE

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps doorkeeper (rubygems), doorkeeper (rubygems), doorkeeper (rubygems), doorkeeper (rubygems). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
doorkeeperrubygems	>=5.0.0 <5.0.3	5.0.3
doorkeeperrubygems	>=5.1.0 <5.1.1	5.1.1
doorkeeperrubygems	>=5.2.0 <5.2.5	5.2.5
doorkeeperrubygems	>=5.3.0 <5.3.2	5.3.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for doorkeeper, doorkeeper, doorkeeper.
Review the reported fix. Update doorkeeper to 5.0.3; doorkeeper to 5.1.1; doorkeeper to 5.2.5; doorkeeper to 5.3.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
May 7, 2020
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

### 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](https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets)), 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

Quoted source text, attributed separately from HOL analysis.