Lucene search
GoogleOSV:CVE-2017-18076HistoryJan 26, 2018 - 7:29 p.m.
CVE-2017-18076
2018-01-2619:29:00
Google
osv.dev
12
EPSS
0.002
Percentile
55.8%
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.
Related
nessus
nessus
Debian DSA-4109-1 : ruby-omniauth - security update
2018-02-12 00:00:00
osv
osv
ruby-omniauth - security update
2018-02-09 00:00:00
Omniauth allows POST parameters to be stored in session
2018-01-29 15:45:28
debian
debian
[SECURITY] [DSA 4109-1] ruby-omniauth security update
2018-02-10 02:35:38
[SECURITY] [DSA 4109-1] ruby-omniauth security update
2018-02-10 02:35:38
cve
cve
CVE-2017-18076
2018-01-26 19:29:00
veracode
veracode
Cross-Site Request Forgery (CSRF) Via Leakage Of Authenticity Token
2017-01-26 01:44:37
debiancve
debiancve
CVE-2017-18076
2018-01-26 19:29:00
ubuntucve
ubuntucve
CVE-2017-18076
2018-01-26 00:00:00
prion
prion
Session fixation
2018-01-26 19:29:00
openvas
openvas
Debian: Security Advisory (DSA-4109-1)
2018-02-08 00:00:00
cvelist
cvelist
CVE-2017-18076
2018-01-26 19:00:00
github
github
Omniauth allows POST parameters to be stored in session
2018-01-29 15:45:28
nvd
nvd
CVE-2017-18076
2018-01-26 19:29:00
rubygems
rubygems
omniauth leaks authenticity token in callback params
2017-01-10 21:00:00