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.
Published · last modified .
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.
EPSS exploit prediction
EPSS: 0.021 (81.8th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 82nd percentile — 81.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.021 · newest: 0.021 · change: 0.000
Affected products
- Omniauth
- Debian Linux — versions 8.0, 9.0
Public proof-of-concept exploits
References
- github.com/omniauth/omniauth/pull/867 (Patch, Third Party Advisory)
- www.debian.org/security/2018/dsa-4109 (vendor-advisory, Third Party Advisory)
- bugs.debian.org/888523 (Third Party Advisory, Issue Tracking)
- github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c4305144… (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.