PatchTheCVEfaye vulnerabilities and fixes
Recent CVEs affecting faye, with upgrade or downgrade steps. 2 tracked.
faye has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2020-07-31. Highest priority: CVE-2020-11020 (score 54/100).
- CVE-2020-15134 HIGH 8.0 UPGRADE Faye before version 1.4.0, there is a lack of certification validation in TLS handshakes
- CVE-2020-11020 HIGH 8.5 UPGRADE UPGRADE Faye (NPM, RubyGem) versions greater than 0.5.0 and before 1.0.4, 1.1.3 and 1.2.5, has the potential for authe
FAQ
How do I fix faye vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is faye being exploited right now?
None of the tracked faye CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which faye CVE should I patch first?
CVE-2020-11020 currently ranks highest (54/100): Faye (NPM, RubyGem) versions greater than 0.5.0 and before 1.0.4, 1.1.3 and 1.2.5, has the potential for authe.