CVE-2017-18076 Omniauth allows POST parameters to be stored in session
Attackers can bypass CSRF protection in OmniAuth by exploiting improper handling of POST parameters in the callback phase.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-18076?
CVE-2017-18076 is a high-severity vulnerability in Debian Debian Linux, published on 26 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2017-18076?
2 open source packages ship an affected version, including omniauth. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
omniauth RubyGems | All versions | 1.3.2 |
omniauth RubyGems | All versions | 1.3.2 |
Products include Debian Debian Linux, Omniauth Omniauth.
How do I fix CVE-2017-18076?
Upgrade omniauth to 1.3.2 or later.
Is CVE-2017-18076 being exploited?
There is no known exploitation of CVE-2017-18076 in the wild and no public exploit code.
Other vulnerabilities in Debian Debian Linux
Sources
Also known as DEBIAN-CVE-2017-18076, DSA-4109-1, GHSA-9pr6-grf4-x2fr, UBUNTU-CVE-2017-18076.