CVE-2020-15134
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.
Weakness
- CWE-295: Improper Certificate Validation
Timeline
- 2020-07-31Published by the CNA17:40 UTC
- 2020-07-31GitHub advisory published (GHSA-3q49-h8f9-9fr9)same day
Exploit and advisory records
GitHub advisory GHSA-3q49-h8f9-9fr9, affected packages:
| Package | Vulnerable versions | Fixed in |
|---|---|---|
| RubyGems faye | before 1.4.0 | 1.4.0 |
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| faye_project faye | before 1.4.0fixed in 1.4.0 | 1.4.0 |
References
- https://blog.jcoglan.com/2020/07/31/missing-tls-verification-in-faye/
- https://github.com/faye/faye/security/advisories/GHSA-3q49-h8f9-9fr9
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2020-15134'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2020-15134'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2020-15134'curl 'https://api.contrastcyber.com/cve_products/CVE-2020-15134'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).