Loading...
Skip to main content

CVE-2017-18076 — Vulnerability in omniauth — CVE Details

HIGH

Omniauth allows POST parameters to be stored in session

Published January 29, 2018Updated December 3, 2024Source: osv

Summary

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.

Advisory Timeline

  • First published January 29, 2018 (3178 days ago).
  • Last revised December 3, 2024 — 2500 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Bundler
Update omniauth to 1.3.2 or later
gem install omniauth -v 1.3.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: rubygems (1).

PackageEcosystemAffectedFixed In
omniauth
rubygems
0.0.1, 0.0.3, 0.0.4, 0.0.5 (+40 more)1.3.2

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Frequently Asked Questions

What is CVE-2017-18076?
Omniauth allows POST parameters to be stored in session This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.5/10).
How do I check if my project is affected by CVE-2017-18076?
CVE-2017-18076 affects omniauth. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2017-18076 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.5

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-9pr6-grf4-x2fr

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies