CVE-2017-18076: Omniauth Omniauth Allows POST Parameters To Vulnerability

HIGH
Advisory Identifier: GHSA-9pr6-grf4-x2fr
CVSS 7.5
Published
Advisory Summary

CVE-2017-18076 is a HIGH (CVSS 7.5) omniauth allows post parameters to vulnerability (General Security Weakness) affecting Omniauth libraries in the RubyGems ecosystem. The issue involves omniauth allows post parameters to be stored in session. Remediation is available by upgrading affected packages to version 1.3.2.

CVE-2017-18076 at a Glance

CVE Identifier CVE-2017-18076
GHSA Identifier GHSA-9pr6-grf4-x2fr
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification General Security Weakness
Affected Product Omniauth
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2017-18076

To remediate this vulnerability, upgrade all affected Omniauth dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

omniauth fixed: 1.3.2
Upgrade omniauth to 1.3.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for omniauth

How to Check if You Are Affected

To determine whether your application is affected by CVE-2017-18076, inspect your project dependencies for Omniauth:

inspect dependencies for omniauth

Analyze the terminal output to locate any version of Omniauth in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Omniauth, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.

CVE-2017-18076 Affected Omniauth Versions

1 component(s)
Fixed Versions:
1.3.2
Product / Package Ecosystem Affected Versions Fixed Version
omniauth
RubyGems
< 1.3.2
1.3.2

References

Frequently Asked Questions

What is CVE-2017-18076?
CVE-2017-18076 is a security vulnerability in Omniauth involving Omniauth allows POST parameters to be stored in session under General Security Weakness.
Which Omniauth versions are affected?
Affected versions include releases prior to 1.3.2 across affected packages: omniauth.
What version fixes CVE-2017-18076?
Upgrading to 1.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is omniauth affected?
Yes, omniauth is affected in releases prior to 1.3.2. Upgrade your dependency to 1.3.2 or later.
What is the CVSS score of CVE-2017-18076?
CVE-2017-18076 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2017-18076?
CVE-2017-18076 is classified under General Security Weakness.
How can I check RubyGems dependencies for CVE-2017-18076?
Run the dependency tree command: 'inspect dependencies for omniauth'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9pr6-grf4-x2fr",
  "modified" : "2022-04-25T22:27:19Z",
  "published" : "2018-01-29T15:45:28Z",
  "aliases" : [ "CVE-2017-18076" ],
  "summary" : "Omniauth allows POST parameters to be stored in session",
  "details" : "In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "omniauth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2017-18076"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omniauth/omniauth/pull/867"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b"
  }, {
    "type" : "WEB",
    "url" : "https://bugs.debian.org/888523"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/omniauth/omniauth"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth/CVE-2017-18076.yml"
  }, {
    "type" : "WEB",
    "url" : "https://www.debian.org/security/2018/dsa-4109"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:29:12Z",
    "nvd_published_at" : null
  }
}