CVE-2020-36599: OmniAuth's `lib/omniauth/failure_endpoint.rb` does not escape `message_key` value

CVE-2020-36599 · Severity: low · CVSS 3.1 · Published 2022-08-19

OmniAuth's `lib/omniauth/failure_endpoint.rb` does not escape `message_key` value

Technologies: omniauth (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2020-36599 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-36599 being exploited in the wild.
How severe is CVE-2020-36599?
Low severity, with a CVSS score of 3.1, published 19 August 2022.
Which products and versions are affected?
omniauth (RubyGems) ECOSYSTEM:introduced=0,fixed=1.9.2.
Is there a fix for CVE-2020-36599?
Yes. omniauth (RubyGems): upgrade to 1.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-36599?
Check whether you run omniauth (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

  • omniauth (RubyGems): upgrade to 1.9.2 or later
    bundle update omniauth

Affected products

  • omniauth (RubyGems) ECOSYSTEM:introduced=0,fixed=1.9.2

Identifiers

  • CVE-2020-36599
  • GHSA-pm55-qfxr-h247

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