LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9284: The request phase of the OmniAuth Ruby gem (1.9.1 and earlier) is vulnerable to Cross-Site Request Forgery...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Rails applications using the OmniAuth Ruby gem could let an attacker connect a secondary login account to a victim account without the victim intending it. That secondary account may then be able to sign in as the primary account. This is an account takeover risk, not just a nuisance login issue.

Executive priority

Treat this as high priority where OmniAuth supports customer or employee login. The business impact is potential unauthorized access through account linking, especially in externally reachable Rails applications.

Technical view

CVE-2015-9284 is a CWE-352 CSRF flaw in OmniAuth's request phase when used with Ruby on Rails. The CVE text names OmniAuth 1.9.1 and earlier, while the affected record also says all versions, so version scope should be confirmed against vendor guidance.

Likely exposure

Exposure is most likely in Rails applications that use OmniAuth for third-party authentication or account linking, especially older integrations following the vulnerable request-phase behavior.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Public references describe the issue and remediation discussions, but no exploit status is provided here.

Researcher notes

The record provides no CVSS score. The key ambiguity is affected-version scope: the narrative states OmniAuth 1.9.1 and earlier, but the affected array says all versions. Validate against OmniAuth's resolution page and related pull requests.

Mitigation direction

  • Inventory Rails applications using OmniAuth for authentication or account linking.
  • Check installed OmniAuth versions and integration patterns against vendor CVE guidance.
  • Apply OmniAuth's published CVE-2015-9284 resolution guidance.
  • Review account-linking flows for missing user intent checks and CSRF protections.
  • Prioritize remediation for internet-facing applications with social login enabled.

Validation and detection

  • Confirm whether any Rails app uses OmniAuth 1.9.1 or earlier.
  • Verify authentication request flows require intentional user action.
  • Check whether account linking can occur without visible user confirmation.
  • Review tests for CSRF coverage on authentication and account-connection routes.
  • Confirm remediation against OmniAuth's CVE resolution documentation.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-9284 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aomniauth ruby gemAll versionsListed
Weakness

CWE details

CWE-352

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs