ubuntu-cve-2020-15133
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-faye-websocket",
"binary_version": "0.10.7-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "ruby-faye-websocket",
"purl": "pkg:deb/ubuntu/ruby-faye-websocket@0.10.7-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.10.7-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-faye-websocket",
"binary_version": "0.11.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "ruby-faye-websocket",
"purl": "pkg:deb/ubuntu/ruby-faye-websocket@0.11.0-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-faye-websocket",
"binary_version": "0.11.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "ruby-faye-websocket",
"purl": "pkg:deb/ubuntu/ruby-faye-websocket@0.11.0-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-faye-websocket",
"binary_version": "0.11.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "ruby-faye-websocket",
"purl": "pkg:deb/ubuntu/ruby-faye-websocket@0.11.0-1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-faye-websocket",
"binary_version": "0.11.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "ruby-faye-websocket",
"purl": "pkg:deb/ubuntu/ruby-faye-websocket@0.11.0-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0-1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2020-15133",
"modified": "2026-05-20T14:52:15Z",
"published": "2020-07-31T18:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2020-15133"
},
{
"type": "REPORT",
"url": "https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv"
},
{
"type": "REPORT",
"url": "https://github.com/faye/faye-websocket-ruby/pull/129"
},
{
"type": "REPORT",
"url": "https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-15133"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2020-15133"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.