watchdogdevelopment vulnerabilities
Recent CVEs affecting watchdogdevelopment products. 4 tracked.
watchdogdevelopment has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-02-05. Highest priority: CVE-2017-15921 (score 60/100).
- CVE-2018-6627 HIGH 7.8 DOWNGRADE In WatchDog Anti-Malware 2.74.186.150, the driver file (ZAMGUARD32.SYS) allows local users to cause a denial o
- CVE-2018-6625 HIGH 7.8 DOWNGRADE In WatchDog Anti-Malware 2.74.186.150, the driver file (ZAMGUARD32.SYS) allows local users to cause a denial o
- CVE-2017-15921 HIGH 7.5 DOWNGRADE DOWNGRADE In Watchdog Anti-Malware 2.74.186.150 and Online Security Pro 2.74.186.150, the zam32.sys driver contains a NU
- CVE-2017-15920 HIGH 7.5 DOWNGRADE DOWNGRADE In Watchdog Anti-Malware 2.74.186.150 and Online Security Pro 2.74.186.150, the zam32.sys driver contains a NU
FAQ
How do I fix watchdogdevelopment 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 watchdogdevelopment being exploited right now?
None of the tracked watchdogdevelopment CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which watchdogdevelopment CVE should I patch first?
CVE-2017-15921 currently ranks highest (60/100): In Watchdog Anti-Malware 2.74.186.150 and Online Security Pro 2.74.186.150, the zam32.sys driver contains a NU.