# CVE-2012-6134: omniauth-oauth2 Cross-Site Request Forgery vulnerability

> Remote attackers can hijack user authentication sessions via CSRF in the omniauth-oauth2 Ruby gem, requiring user interaction to modify session state.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Apr 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fgmx-8h93-26fh

## What is CVE-2012-6134?

CVE-2012-6134 is a medium-severity vulnerability in n/a, published on 9 Apr 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2012-6134?

2 open source packages ship an affected version, including omniauth-oauth2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `omniauth-oauth2` | RubyGems | All versions | 1.1.1 |
| `omniauth-oauth2` | RubyGems | All versions | 1.1.1 |

Products: Omniauth-Oauth2 Project Omniauth-Oauth2.

## How do I fix CVE-2012-6134?

Upgrade omniauth-oauth2 to 1.1.1 or later.

## Is CVE-2012-6134 being exploited?

There is no known exploitation of CVE-2012-6134 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6134 and fix it if it is affected.

What it is: CVE-2012-6134 is a medium-severity vulnerability in n/a, published on 9 Apr 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-6134 in the wild and no public exploit code.

Affected packages and fixed versions:
- omniauth-oauth2 (RubyGems): affected all versions; fixed in 1.1.1
- omniauth-oauth2 (RubyGems): affected all versions; fixed in 1.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-6134/ (Markdown: https://insights.sbomify.com/CVE-2012-6134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-6134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-6134
- OSV: https://osv.dev/vulnerability/CVE-2012-6134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-6134/
Summaries are generated and may contain mistakes; the official description above is the record.