trackercam vulnerabilities and fixes
Recent CVEs affecting trackercam, with upgrade or downgrade steps. 5 tracked.
trackercam has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2005-03-30. Highest priority: CVE-2005-0478 (score 47/100).
- CVE-2005-0482 MEDIUM 5.0 UPGRADE TrackerCam 5.12 and earlier allows remote attackers to cause a denial of service (crash) via (1) a large numbe
- CVE-2005-0481 MEDIUM 5.0 UPGRADE TrackerCam 5.12 and earlier allows remote attackers to read log files via the fn parameter in a direct request
- CVE-2005-0480 MEDIUM 4.3 UPGRADE Cross-site scripting (XSS) vulnerability in TrackerCam 5.12 and earlier allows remote attackers to inject arbi
- CVE-2005-0479 MEDIUM 5.0 UPGRADE Directory traversal vulnerability in ComGetLogFile.php3 for TrackerCam 5.12 and earlier allows remote attacker
- CVE-2005-0478 MEDIUM 5.0 UPGRADE Multiple buffer overflows in TrackerCam 5.12 and earlier allow remote attackers to cause a denial of service a
FAQ
How do I fix trackercam 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 trackercam being exploited right now?
None of the tracked trackercam CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which trackercam CVE should I patch first?
CVE-2005-0478 currently ranks highest (47/100): Multiple buffer overflows in TrackerCam 5.12 and earlier allow remote attackers to cause a denial of service a.