omniauth 1.1.2

3 security vulnerabilities found in version 1.1.2

OmniAuth's lib/omniauth/failure_endpoint.rb does not escape message_key value

critical severity CVE-2020-36599
critical severity CVE-2020-36599
Patched versions: ~> 1.9.2, >= 2.0.0

lib/omniauth/failure_endpoint.rb in OmniAuth before 1.9.2 (and before 2.0) does not escape the message_key value.

omniauth leaks authenticity token in callback params

high severity CVE-2017-18076
high severity CVE-2017-18076
Patched versions: >= 1.3.2

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.

CSRF vulnerability in OmniAuth's request phase

high severity CVE-2015-9284
high severity CVE-2015-9284
Patched versions: >= 2.0.0

The request phase of the OmniAuth Ruby gem is vulnerable to Cross-Site Request Forgery (CSRF) 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.

In order to mitigate this vulnerability, Rails users should consider using the omniauth-rails_csrf_protection gem.

More info is available here: https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284

No officially reported memory leakage issues detected.


This gem version does not have any officially reported memory leaked issues.

No license issues detected.


This gem version has a license in the gemspec.

This gem version is available.


This gem version has not been yanked and is still available for usage.