Description

Faye before version 1.4.0, there is a lack of certification validation in TLS handshakes. Faye uses em-http-request and faye-websocket in the Ruby version of its client. Those libraries both use 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 `https:` or `wss:` connection made using these libraries is vulnerable to a man-in-the-middle attack, since it does not confirm the identity of the server it is connected to. The first request a Faye client makes is always sent via normal HTTP, but later messages may be sent via WebSocket. Therefore it is vulnerable to the same problem that these underlying libraries are, and we needed both libraries to support TLS verification before Faye could claim to do the same. Your client would still be insecure if its initial HTTPS request was verified, but later WebSocket connections were not. This is fixed in Faye v1.4.0, which enables verification by default. For further background information on this issue, please see the referenced GitHub Advisory.

Metrics

 

CVSS Version 4.0 CVSS Version 3.x CVSS Version 2.0

NVD enrichment efforts reference publicly available information to associate vector strings. CVSS information contributed by other sources is also displayed.

CVSS 4.0 Severity and Vector Strings:

NIST: NVD

N/A

NVD assessment not yet provided.

CVSS 3.x Severity and Vector Strings:

NIST: NVD

Base Score:  8.7 HIGH

Vector:  CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

CNA:  GitHub, Inc.

Base Score:  8.0 HIGH

Vector:  CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

CVSS 2.0 Severity and Vector Strings:

NIST: NVD

Base Score:  6.4 MEDIUM

Vector:  (AV:N/AC:L/Au:N/C:P/I:P/A:N)

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Hyperlink	Resource
https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/	Exploit  Third Party Advisory
https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9	Exploit  Third Party Advisory

Weakness Enumeration

CWE-ID	CWE Name	Source
CWE-295	Improper Certificate Validation	NIST   GitHub, Inc.

Known Affected Software Configurations Switch to CPE 2.2

CPEs loading, please wait.

Denotes Vulnerable Software
Are we missing a CPE here? Please let us know.

Change History

2 change records found show changes

CVE Modified by GitHub, Inc. 5/14/2024 2:29:56 AM

Action	Type	Old Value	New Value

Initial Analysis by NIST 8/11/2020 1:15:09 PM

Action	Type	Old Value	New Value
Added	CPE Configuration		OR *cpe:2.3:a:faye_project:faye:*:*:*:*:*:*:*:* versions up to (excluding) 1.4.0
Added	CVSS V2		NIST (AV:N/AC:L/Au:N/C:P/I:P/A:N)
Added	CVSS V2 Metadata		Access Complexity Insufficient Information
Added	CVSS V3.1		NIST AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
Added	CWE		NIST CWE-295
Changed	Reference Type	https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/ No Types Assigned	https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/ Exploit, Third Party Advisory
Changed	Reference Type	https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9 No Types Assigned	https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9 Exploit, Third Party Advisory