Vulnerability in Doorkeeper (CVE-2020-10187)
Summary
Vulnerability in Doorkeeper (CVE-2020-10187). Confidential information can be exposed externally. Exploitable via GET /oauth/authorized_applications.json.
Original description
The description as published by the source.
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
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-10187 has been found in Doorkeeper.
Attackers can target a specific entry point like GET /oauth/authorized_applications.json over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Doorkeeper CVE-2020-10187" on the vendor's site.
CVE-2020-10187 (Doorkeeper)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /oauth/authorized_applications.json
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in Doorkeeper. Attackers reach the vulnerable code path via GET /oauth/authorized_applications.json without authentication.
Check the vendor advisory for the affected versions of Doorkeeper. Attack surface: GET /oauth/authorized_applications.json.
Severity: ?. Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /oauth/authorized_applications.json requests with malformed payloads or SQL meta-characters. Run grep -r 'Doorkeeper' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Doorkeeper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Doorkeeperを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /oauth/authorized_applications.json' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /oauth/authorized_applications.jsonへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /oauth/authorized_applications.json on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2020-10187 ruby-doorkeeper Fixed in: 5.0.3-1
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com