
Typically arrogant behaviour by this vendor. It seems they knew about it a fair time before they admitted to it, and partners still have not received any push communication beyond what is on their public site. Do they deserve our business?
Two security firms have found what they believe to be a supply chain attack on communications software maker 3CX – and the vendor's boss is advising users to switch to the progressive web app until the 3CX desktop client is updated. 3CX started as a vendor of PBX software, and evolved to offer voice, video, and …
These shitbags are trying to cover this up. They're downplaying it on social media, they haven't informed their customers (many of whom will have been running a trojan for well over a week!) and they ignored it on their forums for a week before basically replying "take it up with your antivirus company" (you really should see this exchange for yourself, go look at their forum, it's really quite something!).
We use 3CX. We weren't affected by this because we don't use the desktop client. We started looking at alternatives this afternoon!
"3CX Hosted and StartUP users do not need to update their servers as we will be updating them over the night automatically. Servers will be restarted and the new Electron App MSI/DMG will be installed on the server. We recommend that you DO NOT install or deploy the Electron App. This update is only to ensure that the trojan has been removed from the 3CX Server where Desktop Apps are stored and in case any users decide to deploy the app anyway. During the restart there might be disruption for a few minutes while we restart your server."
"...You must love patching if you think that using desktop apps for everything is the way to go..."
Or, you know, if you read some of the forums, you'd know that some of 3CX's users need and use functionality that is currently only available in the desktop application.
Easy to criticise without all of the facts.
3CX do completely managed (As in, non self-hosted - As in, in their cloud) PBX's as well (StartUP) so I'm afraid you've missed the mark again. Possibly best not to comment on something you're not particular familiar with.
(Disclaimer, 3CX Partner - Don't work for 3CX, just fear that someone at 3CX may be reading my posts and Nick Galea will knee-jerk revoke my partner status, ban me from their forums as he has several others in times gone by - AND then e-mail all my customers directly to sell them...)
Step 1 - Ignore it and hope it'll go away.
Step 2- Deny it. Claim it's a false positive.
Step 3 - Admit it, but don't say anything useful.
Step 4 - Argue with customers who need actual information and not marketing spin.
Step 5 - Watch as those same customers plan their migrations.
We are (or perhaps that should be were) a 3cx reseller & user. Their handling of this incident has been poor to say the least - poor disclosure, poor communication, poor remediation. Ok, this impacted a part of their offering that thankfully few of our clients actually use but that's not the point - if I can't trust their vulnerability handling processes I can't trust their application.
int main(enter the void)
...