{"api_version":"1","generated_at":"2026-07-23T12:56:43+00:00","cve":"CVE-2020-15133","urls":{"html":"https://cve.report/CVE-2020-15133","api":"https://cve.report/api/cve/CVE-2020-15133.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2020-15133","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-15133"},"summary":{"title":"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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2020-07-31 18:15:00","updated_at":"2021-11-18 18:28:00"},"problem_types":["CWE-295"],"metrics":[],"references":[{"url":"https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv","name":"https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv","refsource":"CONFIRM","tags":["Exploit","Third Party Advisory"],"title":"Missing TLS certificate verification · Advisory · faye/faye-websocket-ruby · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"0"},{"url":"https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/","name":"https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"Missing TLS certificate verification in Faye – The If Works","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-15133","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15133","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2020","cve_id":"15133","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"faye-websocket_project","cpe5":"faye-websocket","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2020","cve_id":"15133","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"faye-websocket_project","cpe5":"faye-websocket","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2020-15133","qid":"180782","title":"Debian Security Update for ruby-faye-websocket (CVE-2020-15133)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2020-15133","STATE":"PUBLIC","TITLE":"Missing TLS certificate verification in Faye Websocket"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"faye-websocket","version":{"version_data":[{"version_value":"< 0.11.0"}]}}]},"vendor_name":"faye"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":8,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-295: Improper Certificate Validation"}]}]},"references":{"reference_data":[{"name":"https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/","refsource":"MISC","url":"https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/"},{"name":"https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv","refsource":"CONFIRM","url":"https://github.com/faye/faye-websocket-ruby/security/advisories/GHSA-2v5c-755p-p4gv"}]},"source":{"advisory":"GHSA-2v5c-755p-p4gv","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2020-07-31 18:15:00","lastModifiedDate":"2021-11-18 18:28:00","problem_types":["CWE-295"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":8.7,"baseSeverity":"HIGH"},"exploitabilityScore":2.2,"impactScore":5.8},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:P/I:P/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":5.8},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":4.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:faye-websocket_project:faye-websocket:*:*:*:*:*:*:*:*","versionEndExcluding":"0.11.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2020","CveId":"15133","Ordinal":"176512","Title":"CVE-2020-15133","CVE":"CVE-2020-15133","Year":"2020"},"notes":[{"CveYear":"2020","CveId":"15133","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2020","CveId":"15133","Ordinal":"2","NoteData":"2020-07-31","Type":"Other","Title":"Published"},{"CveYear":"2020","CveId":"15133","Ordinal":"3","NoteData":"2020-07-31","Type":"Other","Title":"Modified"}]}}}