Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2020-15134— Missing TLS certificate verification in Faye

Quick assessment

Affected
faye faye
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Faye是James Coglan软件开发者的一套开源的基于Bayeux协议的发布-订阅消息系统。该系统主要用于在Web客户端之间进行发布-订阅消息传递。 Faye 1.4.0之前版本中存信任管理问题漏洞，该漏洞源于在TLS握手过程中，程序没有进行证书检查。攻击者可利用该漏洞实施中间人攻击。

CVSS 8.0 · High EPSS 0.86% · P56
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2020-15134

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Missing TLS certificate verification in Faye
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
证书验证不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Faye 信任管理问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Faye是James Coglan软件开发者的一套开源的基于Bayeux协议的发布-订阅消息系统。该系统主要用于在Web客户端之间进行发布-订阅消息传递。 Faye 1.4.0之前版本中存信任管理问题漏洞，该漏洞源于在TLS握手过程中，程序没有进行证书检查。攻击者可利用该漏洞实施中间人攻击。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
faye faye < 1.4.0 -

II. Public POCs for CVE-2020-15134

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-15134

请登录查看更多情报信息。

Vendor Advisories for CVE-2020-15134 (1)

Security Blog Posts for CVE-2020-15134 (1)

IV. Related Vulnerabilities

Same product: faye
Same vendor: faye
Same weakness: CWE-295

V. Comments for CVE-2020-15134

No comments yet

Leave a comment