v-secure vulnerabilities
Recent CVEs affecting v-secure products. 5 tracked.
v-secure has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2020-11-23. Highest priority: CVE-2018-16723 (score 34/100).
- CVE-2018-16723 HIGH 7.8 DOWNGRADE In Jingyun Antivirus v2.4.2.39, the driver file (ZySandbox.sys) allows local users to cause a denial of servic
- CVE-2018-16722 HIGH 7.8 DOWNGRADE In Jingyun Antivirus v2.4.2.39, the driver file (ZySandbox.sys) allows local users to cause a denial of servic
- CVE-2018-16721 HIGH 7.8 DOWNGRADE In Jingyun Antivirus v2.4.2.39, the driver file (ZySandbox.sys) allows local users to cause a denial of servic
- CVE-2018-16720 HIGH 7.8 DOWNGRADE In Jingyun Antivirus v2.4.2.39, the driver file (ZySandbox.sys) allows local users to cause a denial of servic
- CVE-2018-16719 HIGH 7.8 DOWNGRADE In Jingyun Antivirus v2.4.2.39, the driver file (hookbody.sys) allows local users to cause a denial of service
FAQ
How do I fix v-secure 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 v-secure being exploited right now?
None of the tracked v-secure CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which v-secure CVE should I patch first?
CVE-2018-16723 currently ranks highest (34/100): In Jingyun Antivirus v2.4.2.39, the driver file (ZySandbox.sys) allows local users to cause a denial of servic.