Skip to content
OpenAdvisories
High · 8.0 CVE-2020-15133 EUVD-2020-0529GHSA-2v5c-755p-p4gv

Missing TLS certificate verification in Faye Websocket

Published Jul 31, 2020 · Updated Aug 4, 2024 · Assigned by GitHub_M

Description

In faye-websocket before version 0.11.0, there is a lack of certification validation in TLS handshakes. The `Faye::WebSocket::Client` class uses the `EM::Connection#start_tls` method in EventMachine to implement the TLS handshake whenever a `wss:` URL is used for the connection. This method does not implement certificate verification by default, meaning that it does not check that the server presents a valid and trusted TLS certificate for the expected hostname. That means that any `wss:` connection made using this library is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to. For further background information on this issue, please see the referenced GitHub Advisory. Upgrading `faye-websocket` to v0.11.0 is recommended.

Affected products

VendorProductAffectedFixed
faye faye-websocket < 0.11.0 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 ruby-faye-websocket 0.11.0-1 —
Debian 13 ruby-faye-websocket 0.11.0-1 —
Debian 12 ruby-faye-websocket 0.11.0-1 —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 ruby-faye-websocket No fix yet —
Ubuntu 26.04 LTS ruby-faye-websocket No fix yet —
Ubuntu 25.10 ruby-faye-websocket No fix yet —
Ubuntu 24.04 LTS ruby-faye-websocket No fix yet —
Ubuntu 22.04 LTS ruby-faye-websocket No fix yet —
Show 1 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu 20.04 LTS ruby-faye-websocket No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
RubyGems faye-websocket < 0.11.0 0.11.0 GHSA-2v5c-755p-p4gv

References