Skip to content

OmniAuth Ruby gem Cross-site Request Forgery in request phase

High severity GitHub Reviewed Published May 29, 2019 to the GitHub Advisory Database • Updated Feb 15, 2024

Package

bundler omniauth (RubyGems)

Affected versions

<= 1.9.2

Patched versions

2.0.0

Description

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.

References

Published by the National Vulnerability Database Apr 26, 2019
Reviewed May 29, 2019
Published to the GitHub Advisory Database May 29, 2019
Last updated Feb 15, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.172%
(54th percentile)

Weaknesses

CVE ID

CVE-2015-9284

GHSA ID

GHSA-ww4x-rwq6-qpgf

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.