PatchTheCVEfreshtomato vulnerabilities and fixes
Recent CVEs affecting freshtomato, with upgrade or downgrade steps. 5 tracked.
freshtomato has 5 tracked vulnerabilities, 4 critical. A fixed release or vendor patch exists for 1. Most recent: 2023-10-16. Highest priority: CVE-2022-42484 (score 68/100).
- CVE-2023-3991 CRITICAL 10.0 MITIGATE An OS command injection vulnerability exists in the httpd iperfrun.cgi functionality of FreshTomato 2023.3
- CVE-2022-42484 CRITICAL 9.8 MITIGATE MITIGATE An OS command injection vulnerability exists in the httpd logs/view.cgi functionality of FreshTomato 2022.5
- CVE-2022-38451 HIGH 7.5 MITIGATE MITIGATE A directory traversal vulnerability exists in the httpd update.cgi functionality of FreshTomato 2022.5
- CVE-2022-28665 CRITICAL 9.8 MITIGATE A memory corruption vulnerability exists in the httpd unescape functionality of FreshTomato 2022.1
- CVE-2022-28664 CRITICAL 9.8 MITIGATE A memory corruption vulnerability exists in the httpd unescape functionality of FreshTomato 2022.1
FAQ
How do I fix freshtomato 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 freshtomato being exploited right now?
None of the tracked freshtomato CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which freshtomato CVE should I patch first?
CVE-2022-42484 currently ranks highest (68/100): An OS command injection vulnerability exists in the httpd logs/view.cgi functionality of FreshTomato 2022.5.