CVE-2018-1000211: Doorkeeper subject to Incorrect Permission Assignment

CVE-2018-1000211 · Severity: low · CVSS 3 · Published 2018-08-13

Doorkeeper subject to Incorrect Permission Assignment

Technologies: doorkeeper (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2018-1000211 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1000211 being exploited in the wild.
How severe is CVE-2018-1000211?
Low severity, with a CVSS score of 3, published 13 August 2018.
Which products and versions are affected?
doorkeeper (RubyGems) ECOSYSTEM:introduced=4.2.0,fixed=4.4.0.
Is there a fix for CVE-2018-1000211?
Yes. doorkeeper (RubyGems): upgrade to 4.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1000211?
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 4.4.0 or later
    bundle update doorkeeper

Affected products

  • doorkeeper (RubyGems) ECOSYSTEM:introduced=4.2.0,fixed=4.4.0

Identifiers

  • CVE-2018-1000211
  • GHSA-694m-jhr9-pf77

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