Skip to content
Fencer Intel
high 7.5

CVE-2020-10187 json

Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper

published 6y ago modified last mo. also GHSA-j7vx-8mqj-cqp9 , EUVD-2020-0426

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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.

Patch / fix

  • rubygems doorkeeper 5.0.3, 5.1.1, 5.2.5, 5.3.2
  • doorkeeper_project doorkeeper 5.0.3, 5.1.1, 5.2.5, 5.3.2
  • ruby-doorkeeper Debian 14, Debian 13, Debian 12 5.0.3-1

debian advisories DEBIAN-CVE-2020-10187

Is CVE-2020-10187 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems doorkeeper
>=5.0.0, <5.0.3
>=5.1.0, <5.1.1
>=5.2.0, <5.2.5
>=5.3.0, <5.3.2
5.0.3
5.1.1
5.2.5
5.3.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.