Faye Websocket
Approved changes feed: RSS · Atom
cpe:2.3:a:faye-websocket_project:faye-websocket:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Faye Websocket Project (f8c7b0cd-383d-521f-a151-e3ae377052b7) |
|---|---|
| Product | Faye Websocket (09d887fb-03e6-583c-9735-df3b4b1a9e0f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15133 |
vulnerable | 2026-06-08 05:19:25.336707 |
Missing TLS certificate verification in Faye Websocket
HIGH (8)
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.
Published: 2020-07-31T17:40:21.000Z
Updated: 2024-08-04T13:08:22.247Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.