CVE-2017-18076
published 2018-01-26CVE-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…
PriorityP337high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
2.13%
80.1th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | ruby-omniauth | < ruby-omniauth 1.3.1-2 (bookworm) | ruby-omniauth 1.3.1-2 (bookworm) |
| omniauth | omniauth | < 1.3.2 | 1.3.2 |
| omniauth | omniauth | >= 0 < 1.3.2 | 1.3.2 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2017-18076: ruby-omniauth - In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is imprope...
vendor_debian·2017·CVSS 7.5
CVE-2017-18076 [HIGH] CVE-2017-18076: ruby-omniauth - In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is imprope...
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.
Scope: local
bookworm: resolved (fixed in 1.3.1-2)
bullseye: resolved (fixed in 1.3.1-2)
forky: resolved (fixed in 1.3.1-2)
sid: resolved (fixed in 1.3.1-2)
trixie: resolved (fixed in 1.3.1-2)
OSV
Omniauth allows POST parameters to be stored in session
osv·2018-01-29
CVE-2017-18076 [HIGH] Omniauth allows POST parameters to be stored in session
Omniauth allows POST parameters to be stored in session
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.
GHSA
Omniauth allows POST parameters to be stored in session
ghsa·2018-01-29
CVE-2017-18076 [HIGH] Omniauth allows POST parameters to be stored in session
Omniauth allows POST parameters to be stored in session
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.
OSV
CVE-2017-18076: In strategy
osv·2018-01-26·CVSS 7.5
CVE-2017-18076 [HIGH] CVE-2017-18076: In strategy
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters
bugzilla·2018-01-30·CVSS 7.5
CVE-2017-18076 [HIGH] CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters
CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters
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.
External References:
https://nvd.nist.gov/vuln/detail/CVE-2017-18076
Upstream Issue:
https://github.com/omniauth/omniauth/pull/867
Upstream Patch:
https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b
Discussion:
Created rubygem-omniauth tracking bugs for this issue:
Affects: fedora-all [bug 1540041]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a packa
Bugzilla
CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters [fedora-all]
bugzilla·2018-01-30·CVSS 7.5
CVE-2017-18076 [HIGH] CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters [fedora-all]
CVE-2017-18076 rubygem-omniauth: Improper protection of authenticity_token in strategy.rb via POST parameters [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: t
https://bugs.debian.org/888523https://github.com/omniauth/omniauth/pull/867https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9bhttps://www.debian.org/security/2018/dsa-4109https://bugs.debian.org/888523https://github.com/omniauth/omniauth/pull/867https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9bhttps://www.debian.org/security/2018/dsa-4109
2018-01-26
Published