CVE-2015-9284: CSRF
The request phase of the OmniAuth Ruby gem (1.9.1 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.
Other sources
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.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2015-9284?
CVE-2015-9284 has been classified as a high severity vulnerability due to its potential to allow Cross-Site Request Forgery attacks.
How do I fix CVE-2015-9284?
To fix CVE-2015-9284, upgrade the OmniAuth Ruby gem to version 2.0.0 or later.
What software is affected by CVE-2015-9284?
CVE-2015-9284 affects versions of the OmniAuth Ruby gem up to and including 1.9.2.
What is the impact of CVE-2015-9284?
The impact of CVE-2015-9284 allows accounts to be connected without user interaction or intent.
How does CVE-2015-9284 exploit the Ruby on Rails framework?
CVE-2015-9284 exploits the request phase in the OmniAuth Ruby gem within the Ruby on Rails framework.