Security Vulnerability within LMInfo.sys
Hi, I have tried to log a support case but the page is constantly reloading therefore I need to post here. Our endpoint security product has detected the lmiinfo.sys as being an potentially u...
Forum Discussion
We took a Windows10 PC with just ESET on it and installed LogmeIn (never on system before) and ESET did not detect anything-ran a custom scan on hte LMI directory too. The LMIinfo.sys in this new install is 11.1.0.3236. When we check the properties for the systems with LMI already installed and updated there is no version information listed. Odd. Could it be we have to uninstall and install LMI on the systems? Hard to do remotely I guess unless we do an ad hoc session to the systems, then uninstall and reinstall LMI?
SOSCOMP After updating the computers did you reboot them? Can you update one and then reboot it and see if ESET still reports an issue? If the driver is in use at the time the update will not be able to replace it fully until the system is rebooted.
We updated LMI manaully and rebooted. Problem still exists. It can be triggered by looking at properties>details of the lmiinfo.sys file (which are blank) or by opening LMI control Panel and going to About>Check for updates, among other triggers. But that is easiest way to see if update worked. When LMI is uninstalled and reinstalled, the properties>Details of the lmiinfo.sys file are not blank -shows version info etc and cannot trigger ESET.
