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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4109-1 | ruby-omniauth security update |
EUVD |
EUVD-2018-0158 | 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. |
Github GHSA |
GHSA-9pr6-grf4-x2fr | Omniauth allows POST parameters to be stored in session |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T21:13:47.519Z
Reserved: 2018-01-26T00:00:00
Link: CVE-2017-18076
No data.
Status : Modified
Published: 2018-01-26T19:29:00.260
Modified: 2024-11-21T03:19:18.537
Link: CVE-2017-18076
No data.
OpenCVE Enrichment
No data.
Debian DSA
EUVD
Github GHSA