Vulnerability in Omniauth

CVE-2017-18076

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.

EPSS: 0.021 (80.0th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Affected products

Public proof-of-concept exploits

References

  • cve@mitre.org (x_refsource_CONFIRM, Patch, Third Party Advisory)
  • cve@mitre.org (vendor-advisory, Third Party Advisory, x_refsource_DEBIAN)
  • cve@mitre.org (x_refsource_CONFIRM, Third Party Advisory, Issue Tracking)
  • cve@mitre.org (x_refsource_CONFIRM, Patch, Third Party Advisory)

Frequently asked questions

What is CVE-2017-18076?
CVE-2017-18076 is a high-severity vulnerability in Omniauth. CVSS score: 7.5/10. Published 2018-01-26.
How severe is CVE-2017-18076?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2017-18076 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.