CVE-2020-15133: Missing TLS certificate verification in Faye Websocket

Published Jul 31, 2020
·
Updated

Faye faye-websocket is vulnerable to a man-in-the-middle attack, caused by the lack of certification validation in TLS handshakes. An attacker could exploit this vulnerability to launch a man-in-the-middle attack and gain access to the communication channel between endpoints to obtain sensitive information or further compromise the system.

Other sources

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#starttls 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 Software

2 affected components
Faye-websocket Project Faye-websocket<0.11.0
IBM Security Verify Governance<=10.0

Event History

Jul 31, 2020
CVE Published
via MITRE·05:40 PM
Data Sourced
via MITRE·05:40 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-15133?

CVE-2020-15133 is a vulnerability in faye-websocket that allows for man-in-the-middle attacks due to the lack of certification validation in TLS handshakes.

2

How severe is CVE-2020-15133?

CVE-2020-15133 has a severity rating of 8.7 (high).

3

What software is affected by CVE-2020-15133?

The Faye-websocket project's faye-websocket version up to and exclusive of 0.11.0 is affected by CVE-2020-15133. Additionally, IBM Security Verify Governance version up to and inclusive of 10.0 is also affected.

4

How does CVE-2020-15133 work?

CVE-2020-15133 occurs when the Faye::WebSocket::Client class in faye-websocket uses the EM::Connection#start_tls method in EventMachine to implement the TLS handshake, but lacks certification validation, making it vulnerable to man-in-the-middle attacks.

5

Is there a fix for CVE-2020-15133?

Yes, updating to version 0.11.0 or higher of faye-websocket resolves the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2020-15133 - Missing TLS certificate verification in Faye Websocket - SecAlerts