Hello.
When I was recently invited to a GotoMeeting I was prompted to download a GotoMeeting Opener.exe file. As part of security best-practices I upload any executable file even from reputable sources to either viruscan.jotti.org or virustotal.com.
When I uploaded the GotoMeeting Opener to VirusTotal, 2/72 antivirus engines report the program is infected: Antiy-AVL reports it is infected by Trojan/Win32.Tiggre, and CyLance reports it is unsafe.
Here is a permalink to the VirusTotal results:
Assuming this is a false-positive detection, can somebody from the company please report this to the 2 antivirus vendors in question? You should be able to reproduce this problem by uploading your own software to virustotal.com.
Thank you.
Solved! Go to Solution.
Hello,
We believe that Cyclance is using a variation of the Windows executable format that may not be the industry standard, and thus causing this confusion. The hash of our signed GoTo Opener exe should only change every 6 months or so.
What I would suggest doing is filing a report with Cyclance support to see what can be done from their side of things.
Our experience has been the hash changes each time you download the file so it is not possible to take any action due to the poor design of the application. ANY other application that was flagged as being bad by antivirus could have the hash shared by the vendor and then you could whitelist it. One would THINK you could install the MSI installer and then use the app installed to join a meeting by ID, but it still insists on shoving the opener program on you.
Options I know about:
Thank you your reply. I have no problem opening the app, so there is no need for me to whitelist it... my point was simply to make LogMeIn aware that one of the VirusTotal scanners is detecting their program as suspicious, so they can take appropriate corrective action (either by fixing their software or telling the antivirus vendor to fix the detection).
I just re-checked, and now exactly one VirusTotal scanner (Cylance) detects the GotoMeeting opener .exe file as unsafe:
Hello,
We believe that Cyclance is using a variation of the Windows executable format that may not be the industry standard, and thus causing this confusion. The hash of our signed GoTo Opener exe should only change every 6 months or so.
What I would suggest doing is filing a report with Cyclance support to see what can be done from their side of things.
Thank you for your reply. I think that you as the software vendor would be in a better position to open a ticket with Cylance as I am not their customer.
In fact the GotoMeeting software works perfectly fine in my environment; I'm a customer of a customer of GotoMeeting whereas I'm a free user of VirusTotal and am not a direct user of Cylance at all. I just happen to use VirusTotal to screen programs (such as yours) that I download in case I accidentally typed the download URL wrong.
@jonathandl Here's their contact page, we don't generally reach out to security vendors ourselves unless there's a provider specific to certan OS: https://www.virustotal.com/gui/contact-us
Um, you are incorrect on the hash not changing for 6 months. The hash changes every time you download the file. As a paying customer for your products, I spent HOURS on the phone with various persons trying to get LogMeIn's attention LAST YEAR. I was told the product was designed to change the hash each time it was downloaded, but no one seemed to know WHY. I was told someone would call me back, but days, weeks, months later no one did. I resolved our drama by whitelisting programs signed by your company, but I held my nose doing it.
Don't just take my word for it:
certutil -hashfile "GoToWebinar Opener-1.exe" SHA1
SHA1 hash of GoToWebinar Opener-1.exe: 8c8697d3a2b7a4676df065040992bcfa5ed9670f
certutil -hashfile "GoToWebinar Opener-2.exe" SHA1
SHA1 hash of GoToWebinar Opener -2.exe: 753328e7eb829df3a99b7d20f378882e73f3b9f1
CertUtil: -hashfile command completed successfully.
I thought the reason the hash changes each time was because the meeting ID is somehow compiled into the code, i.e. it's "hard coded" into the .exe. (I don't know why different instances of the program would be different if they were all for the same participant in the same meeting.) Regardless, it doesn't affect me directly because our security software doesn't block it. But it's security best practice to check downloads against virustotal.com and not run the program if it doesn't come back as clean. Frankly it would make far more sense for LogMeIn, the vendor, to contact the engine vendor directly, rather than me contact VirusTotal since neither VirusTotal nor I really have all that much to do with this, other than just passing information along.
If I wrote a program and sold it to the public then I would take pride in it and contact any antivirus vendor whose engine detects my product to find out why.