CVE-2020-15133

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.

Severity
HIGH
CVSS v3
8.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N · source cna
Exploit chance (EPSS)
0.918%
chance of exploitation in the next 30 days
higher than 60.8% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 2
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2020-07-31Published by the CNA17:40 UTC
  2. 2020-07-31GitHub advisory published (GHSA-2v5c-755p-p4gv)same day

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-2v5c-755p-p4gv, affected packages:

PackageVulnerable versionsFixed in
RubyGems faye-websocketbefore 0.11.00.11.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
faye-websocket_project faye-websocketbefore 0.11.0fixed in 0.11.00.11.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources