Lucene search

K
rubygemsRubySecRUBY:EXCON-2019-16779
HistoryDec 15, 2019 - 9:00 p.m.

Race condition when using persistent connections

2019-12-1521:00:00
RubySec
github.com
12

CVSS2

4.3

Attack Vector

NETWORK

Attack Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

NONE

Availability Impact

NONE

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

CVSS3

5.9

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

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

There was a race condition around persistent connections, where a connection
which is interrupted (such as by a timeout) would leave data on the socket.
Subsequent requests would then read this data, returning content from the
previous response. The race condition window appears to be short, and it
would be difficult to purposefully exploit this.

Users can workaround the problem by disabling persistent connections, though
this may cause performance implications.

Affected configurations

Vulners
Node
rubyexconRange0.71.0
VendorProductVersionCPE
rubyexcon*cpe:2.3:a:ruby:excon:*:*:*:*:*:*:*:*

CVSS2

4.3

Attack Vector

NETWORK

Attack Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

NONE

Availability Impact

NONE

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

CVSS3

5.9

Attack Vector

NETWORK

Attack Complexity

HIGH

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

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