CVE-2020-10187 is a high-severity (CVSS 7.5) CWE-862 vulnerability in doorkeeper. O3 Security confirms whether CVE-2020-10187 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper
Real-World Exposure
doorkeeper💎doorkeeper💎doorkeeper💎doorkeeperReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Doorkeeper version 5.0.0 and later contains an information disclosure vulnerability that allows an attacker to retrieve the client secret only intended for the OAuth application owner. After authorizing the application and allowing access, the attacker simply needs to request the list of their authorized applications in a JSON format (usually GET /oauth/authorized_applications.json). An application is vulnerable if the authorized applications controller is enabled.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | doorkeeper | ≥ 5.0.0&&< 5.0.3 | 5.0.3 |
| 💎RubyGems | doorkeeper | ≥ 5.1.0&&< 5.1.1 | 5.1.1 |
| 💎RubyGems | doorkeeper | ≥ 5.2.0&&< 5.2.5 | 5.2.5 |
| 💎RubyGems | doorkeeper | ≥ 5.3.0&&< 5.3.2 | 5.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doorkeeper. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update doorkeeper to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10187 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-10187 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-10187. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-10187 in your dependencies?
O3 detects CVE-2020-10187 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.