Skip to content
Fencer Vulns
high 7.5

CVE-2017-18076 json

Omniauth allows POST parameters to be stored in session

published 2018-01-26 8 y ago modified 2026-06-17 4 mo ago also GHSA-9pr6-grf4-x2fr , EUVD-2018-0158

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

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.

Patch / fix

  • rubygems omniauth 1.3.2
  • omniauth omniauth 1.3.2
  • ruby-omniauth Debian 14, Debian 13, Debian 12 1.3.1-2

debian advisories DEBIAN-CVE-2017-18076

  • ruby-omniauth Ubuntu 16.04 LTS 1.3.1-1+deb9u1build0.16.04.1

ubuntu advisories UBUNTU-CVE-2017-18076

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-18076 updated cvss 6.5

rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.13% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems omniauth
<1.3.2
1.3.2

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.