PatchTheCVEtomato vulnerabilities and fixes
Recent CVEs affecting tomato, with upgrade or downgrade steps. 1 tracked.
tomato has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-05-16. Highest priority: CVE-2013-7379 (score 50/100).
- CVE-2013-7379 MEDIUM 6.8 UPGRADE The admin API in the tomato module before 0.0.6 for Node.js does not properly check the access key when it is
FAQ
How do I fix tomato 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 tomato being exploited right now?
None of the tracked tomato CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tomato CVE should I patch first?
CVE-2013-7379 currently ranks highest (50/100): The admin API in the tomato module before 0.0.6 for Node.js does not properly check the access key when it is .