CVE-2020-10187: Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper

CVE-2020-10187 · Severity: low · CVSS 3.1 · Published 2020-05-07

Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper

Technologies: doorkeeper (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2020-10187 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-10187 being exploited in the wild.
How severe is CVE-2020-10187?
Low severity, with a CVSS score of 3.1, published 7 May 2020.
Which products and versions are affected?
doorkeeper (RubyGems) ECOSYSTEM:introduced=5.0.0,fixed=5.0.3.
Is there a fix for CVE-2020-10187?
Yes. doorkeeper (RubyGems): upgrade to 5.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-10187?
Check whether you run doorkeeper (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • doorkeeper (RubyGems): upgrade to 5.0.3 or later
    bundle update doorkeeper

Affected products

  • doorkeeper (RubyGems) ECOSYSTEM:introduced=5.0.0,fixed=5.0.3

Identifiers

  • CVE-2020-10187
  • GHSA-j7vx-8mqj-cqp9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.