CVE-2017-18076: Omniauth allows POST parameters to be stored in session

CVE-2017-18076 · Severity: low · CVSS 3.1 · Published 2018-01-29

Omniauth allows POST parameters to be stored in session

Technologies: omniauth (RubyGems). Vendors: RubyGems.

Quick answers

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

Affected products

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

Identifiers

  • CVE-2017-18076
  • GHSA-9pr6-grf4-x2fr

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