# Omniauth allows POST parameters to be stored in session

Advisory record · `GHSA-9pr6-grf4-x2fr`

- **Identifiers:** `GHSA-9pr6-grf4-x2fr` · `CVE-2017-18076`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Published:** 29 Jan 2018
- **Updated:** 3 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jan 2018, 15:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `omniauth` (RubyGems): affected `<1.3.2`; fixed in `1.3.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 82nd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jan 2018. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-9pr6-grf4-x2fr](https://github.com/advisories/GHSA-9pr6-grf4-x2fr)
- [OSV: GHSA-9pr6-grf4-x2fr](https://osv.dev/vulnerability/GHSA-9pr6-grf4-x2fr)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-18076>
- <https://github.com/omniauth/omniauth/pull/867>
- <https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b>
- <https://bugs.debian.org/888523>
- <https://github.com/omniauth/omniauth>
- <https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth/CVE-2017-18076.yml>
- <https://www.debian.org/security/2018/dsa-4109>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9pr6-grf4-x2fr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9pr6-grf4-x2fr/>. Everything for agents: <https://agentprime.io/llms.txt>.