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
HappyHippo Good to see you and thanks for calling this out.
Our team is currently looking into this, we will post an update when we hear more.
Hi Kate,
Do you have any update to share on this? We have also received the same for the rainfo.sys file from LogMeIn - I believe related to the same vulnerability.
C:/Program Files (x86)/LogMeIn/x64/rainfo.sys
D0415ADE5501A645D8A43A0A90AB32A312BD4605
We kindly await for an update and hopefully a date for remediation.
Thanks
Do you have any update to share on this? We have also received the same for the rainfo.sys file from LogMeIn - I believe related to the same vulnerability.
C:/Program Files (x86)/LogMeIn/x64/rainfo.sys
D0415ADE5501A645D8A43A0A90AB32A312BD4605
We kindly await for an update and hopefully a date for remediation.
Thanks
Hi lmiuser12, HappyHippo good to talk with you both.
It’s currently being worked on still and we will begin releasing updates as they become ready. We have to test and make sure each component we update doesn’t introduce any new issues.
I do understand this is of concern. I'll update as I learn further, please feel free to check in as well. Thanks!
Hi Kate,
It's been a few days since the question asked. Did the development team manage to make an update?
Thanks in advance!
ESETtest01 An update has not been released yet, the team is continuing work on this as a high priority. My understanding is there is more than one component to update and we need to test and confirm that no new issues are introduced. We will post announce the update here in the community once it is ready to release.
We have same issue and mos recent update for LogMein did not fix it. We use ESET Endpoint and their support said it was LMI issue-thanks
Hi, I am checking with the team on what the next course of action is. The update itself was quite minor and should have just resulted in the previous LMInfo.sys warning going away.
