Skip to content
Noroxi
CVE-2020-10187· NVD / CVE Program· CNA mitre

Doorkeeper version 5.0.0 and later contains an information disclosure vulnerability that allows an attacker to retrieve the client secret on

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 4, 2020
Updated
Jun 16, 2026
EPSS
2.1% · 81th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

Affected systems

VendorProduct
doorkeeper projectdoorkeeper

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • doorkeeper project doorkeeper5.0.0 and later · before 5.0.3
  • doorkeeper project doorkeeper5.1.0 and later · before 5.1.1
  • doorkeeper project doorkeeper5.2.0 and later · before 5.2.5
  • doorkeeper project doorkeeper5.3.0 and later · before 5.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ruby-doorkeeperbefore 5.0.3-15.0.3-1
RubyGemsdoorkeeperfrom 5.0.0 · before 5.0.35.0.3
RubyGemsdoorkeeperfrom 5.1.0 · before 5.1.15.1.1
RubyGemsdoorkeeperfrom 5.2.0 · before 5.2.55.2.5
RubyGemsdoorkeeperfrom 5.3.0 · before 5.3.25.3.2

Same product

doorkeeper project: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-6582The Doorkeeper gem before 4.2.0 for Ruby might allow remote attackers to conduct replay attacks or revoke arbitrary tokens by leveraging fai
    37Monitor
  • CVE-2018-1000211Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can re
    30Monitor
  • CVE-2014-8144Cross-site request forgery (CSRF) vulnerability in doorkeeper before 1.4.1 allows remote attackers to hijack the authentication of unspecifi
    27Monitor
  • CVE-2023-34246Doorkeeper Improper Authentication vulnerability
    26Monitor
  • CVE-2018-1000088Doorkeeper version 2.1.0 through 4.2.5 contains a Cross Site Scripting (XSS) vulnerability in web view's OAuth app form, user authorization
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-doorkeeper5.0.3-1 · Debian:12Package registry (OSV)
RubyGems:doorkeeper5.0.3Package registry (OSV)
RubyGems:doorkeeper5.1.1Package registry (OSV)
RubyGems:doorkeeper5.2.5Package registry (OSV)
RubyGems:doorkeeper5.3.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records