CVE-2017-18076

HIGHCVSS 7.5/10EPSS 2.14%

Last modified

CVE-2017-18076 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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 estimates a 2.14% chance of exploitation in the next 30 days.

Description

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

CVSS 3.1
7.5/10

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

EPSS Probability
2.14%

79.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
OmniauthOmniauth< 1.3.2
DebianDebian Linux8.0
DebianDebian Linux9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2017-18076?
CVE-2017-18076 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 2.14% probability of exploitation in the next 30 days.
How do I fix CVE-2017-18076?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-18076?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST