Faye
Vendor:
First CVE: Apr 29, 2020 · Active for 6 years
2
Total CVEs
More Total CVEs than 53% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 63% of tracked products
9.3
Avg CVSS
Higher Avg CVSS than 86% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Faye over time
Volume of CVEsAvg CVSS Base Score
First CVE
Apr 29, 2020
6 years ago
Most Recent CVE
Jul 31, 2020
2,187 days ago
CVE Severity & Scoring
Faye2 CVEs
50%
50%
All CVEs352,785 CVEs
45%
40%
11%
HighCritical
Attack Vector
Local0 (0.0%)
Network2 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (50.0%)
High1 (50.0%)
Unknown0 (0.0%)
User Interaction
None2 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None2 (100.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-11020CRITICAL 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 authentication bypass in the extension system. The vulnerability allows any | Apr 29, 2020 | 9.8 | 30 | NO | NO |
CVE-2020-15134HIGH 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 libr | Jul 31, 2020 | 8.7 | 21 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (2 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (2 CVEs).
Media Mentions
Signals from CVEs in this product scope (2 CVEs).
Top CNAs Publishing CVEs For Faye
Top CWEs
Versions
No cataloged versions.