CVE-2017-18076
First published: Fri Jan 26 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| rubygems/omniauth | <1.3.2 | 1.3.2 |
| debian/ruby-omniauth | 1.8.1-1 1.9.1-1 2.1.1-1 | |
| OmniAuth | <1.3.2 | |
| Debian Linux | =8.0 | |
| Debian Linux | =9.0 |
Remedy
https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- 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://www.debian.org/security/2018/dsa-4109
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth/CVE-2017-18076.yml
- https://github.com/advisories/GHSA-9pr6-grf4-x2fr (Advisory)
- https://security-tracker.debian.org/tracker/CVE-2017-18076
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888523
Frequently Asked Questions
What is the severity of CVE-2017-18076?
CVE-2017-18076 has been rated as a moderate severity vulnerability.
How do I fix CVE-2017-18076?
To fix CVE-2017-18076, upgrade OmniAuth to version 1.3.2 or higher.
What software packages are affected by CVE-2017-18076?
CVE-2017-18076 affects OmniAuth versions prior to 1.3.2 and specific Debian package versions including ruby-omniauth.
What is the exploit mechanism for CVE-2017-18076?
CVE-2017-18076 allows for a potential attacker to access the authenticity_token value through improperly stored session variables.
Is there a known workaround for CVE-2017-18076 if I cannot upgrade?
There is no documented workaround for CVE-2017-18076, so upgrading is the recommended approach.
- collector/github-advisory-latest
- alias/GHSA-9pr6-grf4-x2fr
- alias/CVE-2017-18076
- collector/github-advisory
- collector/debian-bugs
- collector/security-tracker-debian
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/references
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/author
- collector/nvd-cve
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- package-manager/rubygems
- package-manager/debian
- vendor/omniauth
- canonical/omniauth
- vendor/debian
- canonical/debian linux
- version/debian linux/8.0
- version/debian linux/9.0