PatchTheCVEvipnet coordinator vulnerabilities and fixes
Recent CVEs affecting vipnet coordinator, with upgrade or downgrade steps. 2 tracked.
Also searched as: vipnetcoordinator.
vipnet coordinator has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-06-15. Highest priority: CVE-2013-3496 (score 33/100).
- CVE-2017-9606 HIGH 7.3 UPGRADE UPGRADE Infotecs ViPNet Client and Coordinator before 4.3.2-42442 allow local users to gain privileges by placing a Tr
- CVE-2013-3496 HIGH 7.2 UPGRADE UPGRADE Infotecs ViPNet Client 3.2.10 (15632) and earlier, ViPNet Coordinator 3.2.10 (15632) and earlier, ViPNet Perso
FAQ
How do I fix vipnet coordinator 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 vipnet coordinator being exploited right now?
None of the tracked vipnet coordinator CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vipnet coordinator CVE should I patch first?
CVE-2013-3496 currently ranks highest (33/100): Infotecs ViPNet Client 3.2.10 (15632) and earlier, ViPNet Coordinator 3.2.10 (15632) and earlier, ViPNet Perso.