CVE-2020-10187: Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper
7.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.61394%
CWE
Published
5/7/2020
Updated
5/4/2023
KEV Status
No
Technology
Ruby
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
doorkeeper | rubygems | >= 5.0.0, < 5.0.3 | 5.0.3 |
doorkeeper | rubygems | = 5.1.0 | 5.1.1 |
doorkeeper | rubygems | >= 5.2.0, < 5.2.5 | 5.2.5 |
doorkeeper | rubygems | >= 5.3.0, < 5.3.2 | 5.3.2 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from the Application model's serialization logic. The commit fix shows the #as_json method was modified to add authorization checks (current_resource_owner validation) and attribute filtering. The workaround instructions explicitly mention patching this method, and the CWE-862 (Missing Authorization) aligns with uncontrolled data exposure via serialization. The controllers (applications_controller.rb) were also updated to pass ownership context, but the root vulnerability lies in the model's serialization method.