CVE-2020-10187: Doorkeeper Project vulnerability
Doorkeeper Project · Doorkeeper
Affected: Doorkeeper Project · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 78% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Doorkeeper Project
- Published
- May 2020
CoverageNo articles yet
No CyberSIXT article names CVE-2020-10187 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-862cwe.mitre.org
- github.com/doorkeeper-gem/doorkeeper/releasesgithub.com
- github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5github.com
- github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-j7github.com
- github.com/rubysec/ruby-advisory-db/pull/446github.com