Snappy
Vendor:
First CVE: Apr 24, 2019 · Active for 7 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
8.1
Avg CVSS
Higher Avg CVSS than 70% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Snappy over time
Volume of CVEsAvg CVSS Base Score
First CVE
Apr 24, 2019
7 years ago
Most Recent CVE
Apr 24, 2019
2,648 days ago
CVE Severity & Scoring
Snappy1 CVEs
100%
All CVEs352,294 CVEs
45%
40%
11%
High
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None0 (0.0%)
Unknown0 (0.0%)
Required1 (100.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2018-7577HIGH Memcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory. | Apr 24, 2019 | 8.1 | 25 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 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 (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Snappy
Top CWEs
Versions
| Version | CVE Count | Avg CVSS | Avg EPSS | KEV | Exploits |
|---|---|---|---|---|---|
| 1.1.4 | 1 | 8.1 | 0.4% | 0 | 0 |