GHSA-WW4X-RWQ6-QPGF

Vulnerability from github – Published: 2019-05-29 19:11 – Updated: 2024-02-15 15:03
VLAI?
Summary
OmniAuth Ruby gem Cross-site Request Forgery in request phase
Details

The request phase of the OmniAuth Ruby gem (1.9.2 and earlier) is vulnerable to Cross-Site Request Forgery when used as part of the Ruby on Rails framework, allowing accounts to be connected without user intent, user interaction, or feedback to the user. This permits a secondary account to be able to sign into the web application as the primary account.

As of v2 OmniAuth no longer has the vulnerable configuration by default, but it is still possible to configure OmniAuth in such a way that the web application becomes vulnerable to Cross-Site Request Forgery. There is a recommended remediation described here.

Severity ?
8.8 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.9.2"
      },
      "package": {
        "ecosystem": "RubyGems",
        "name": "omniauth"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2015-9284"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2019-05-29T19:10:54Z",
    "nvd_published_at": "2019-04-26T15:29:00Z",
    "severity": "HIGH"
  },
  "details": "The request phase of the OmniAuth Ruby gem (1.9.2 and earlier) is vulnerable to Cross-Site Request Forgery when used as part of the Ruby on Rails framework, allowing accounts to be connected without user intent, user interaction, or feedback to the user. This permits a secondary account to be able to sign into the web application as the primary account.\n\nAs of v2 OmniAuth no longer has the vulnerable configuration by default, but it is still possible to configure OmniAuth in such a way that the web application becomes vulnerable to Cross-Site Request Forgery. There is a recommended remediation described [here](https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284).",
  "id": "GHSA-ww4x-rwq6-qpgf",
  "modified": "2024-02-15T15:03:15Z",
  "published": "2019-05-29T19:11:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9284"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth/issues/1031"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth-rails/pull/1"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth/pull/809"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rubysec/ruby-advisory-db/commit/aef9f623c0be838234d53baf18977564804da397"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/omniauth/omniauth"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth/releases/tag/v1.9.2"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth/releases/tag/v2.0.0"
    },
    {
      "type": "WEB",
      "url": "https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth/CVE-2015-9284.yml"
    },
    {
      "type": "WEB",
      "url": "https://www.openwall.com/lists/oss-security/2015/05/26/11"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "OmniAuth Ruby gem Cross-site Request Forgery in request phase"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.