CVE-2017-18076
Omniauth allows POST parameters to be stored in session
Reported by mitre · Published January 26, 2018
omniauth is fixed in 1.3.2 (RubyGems)
In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| omniauth | RubyGems | 1.3.2 |
| omniauth | omniauth | 1.3.2 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
| RubyGems | omniauth | 0 |
Timeline
- Jan 26, 2018 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Nov 21, 2024 CVE Updated
- Mar 17, 2026 Security Advisory (2 in total, the first dated here)
- Apr 10, 2026 Distribution Patch
- Oct 1, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2017-18076
vulnetix vdb fixes CVE-2017-18076
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-18076/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_CONFIRM
- DSA-4109 vendor-advisoryx_refsource_DEBIAN
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- https://nvd.nist.gov/vuln/detail/CVE-2017-18076 advisory