CVE-2012-6134 json
omniauth-oauth2 Cross-Site Request Forgery vulnerability
published 2013-04-09 13 y ago modified 2026-06-16 4 mo ago also GHSA-fgmx-8h93-26fh , EUVD-2017-0228
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Cross-site request forgery (CSRF) vulnerability in the omniauth-oauth2 gem 1.1.1 and earlier for Ruby allows remote attackers to hijack the authentication of users for requests that modify session state.
Patch / fix
- rubygems omniauth-oauth2 1.1.1
- omniauth-oauth2_project omniauth-oauth2 1.1.1
- github.com/Shopify/omniauth-shopify-oauth2#1 pull request
- github.com/intridea/omniauth-oauth2#25 pull request
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | omniauth-oauth2 | <1.1.1 |
1.1.1 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/Shopify/omniauth-shopify-oauth2/pull/1
web, patch, third-party-advisory
-
github.com
/intridea/omniauth-oauth2/pull/25
web, patch, third-party-advisory
-
rubysec.github.io
/advisories/CVE-2012-6134/
broken-link
-
gist.github.com
/homakov/3673012
broken-link
-
seclists.org
/oss-sec/2013/q1/304
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2012-6134
advisory
-
github.com
/Shopify/omniauth-shopify-oauth2
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/omniauth-oauth2/CVE-2012-6134.yml
web
-
web.archive.org
/web/20170312020947/https://gist.github.com/homakov/3673012
web
-
rubysec.github.io
/advisories/CVE-2012-6134
web
Sources
- CVE List CVE-2012-6134
- GitHub Advisory GHSA-fgmx-8h93-26fh
- NVD CVE-2012-6134
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.