Lucene search

K
rubygemsRubySecRUBY:OMNIAUTH-2017-18076
HistoryJan 10, 2017 - 9:00 p.m.

omniauth leaks authenticity token in callback params

2017-01-1021:00:00
RubySec
github.com
7

CVSS2

5

Attack Vector

NETWORK

Attack Complexity

LOW

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

NONE

Availability Impact

NONE

AV:N/AC:L/Au:N/C:P/I:N/A:N

CVSS3

7.5

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

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

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 configurations

Vulners
Node
rubyomniauthRange1.3.2
VendorProductVersionCPE
rubyomniauth*cpe:2.3:a:ruby:omniauth:*:*:*:*:*:*:*:*

CVSS2

5

Attack Vector

NETWORK

Attack Complexity

LOW

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

NONE

Availability Impact

NONE

AV:N/AC:L/Au:N/C:P/I:N/A:N

CVSS3

7.5

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

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