Tomato
Vendor:
First CVE: May 16, 2014 · Active for 12 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
6.8
Avg CVSS
Higher Avg CVSS than 36% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Tomato over time
Volume of CVEsAvg CVSS Base Score
First CVE
May 16, 2014
12 years ago
Most Recent CVE
May 16, 2014
4,455 days ago
CVE Severity & Scoring
Tomato1 CVEs
100%
All CVEs352,727 CVEs
45%
40%
11%
Medium
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown1 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown1 (100.0%)
User Interaction
None0 (0.0%)
Unknown1 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown1 (100.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2013-7379MEDIUM The admin API in the tomato module before 0.0.6 for Node.js does not properly check the access key when it is set to a string, which allows remote attackers to bypass authenticatio | May 16, 2014 | 6.8 | 23 | 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 Tomato
Top CWEs
Versions
No cataloged versions.