A few days ago, LowEndTalk member @loay shared a communication from community provider OuiHeberg that their client area had been breached. They run WHMCS and use both Proxmox and Virtualizor for their virtualization management.
OuiHeberg noticed the breach and took all the sensible measures – forcing password resets, migrating some customers to fresh servers, notifying authorities, and communicating with their users. So kudos to OuiHeberg for handling the situation properly and being transparent. They noted that their Virtualizor infrastructure (about 25% of their fleet) “shows a much higher level of compromise” and that “Virtualizor is “now considered to be the entry point of the attack”.
But then the drama started.
On November 13, @virtualizor commented:
We would just like to add that this security breach is not caused by Virtualizor as per the details shared by the Ouiheberg team.
Our internal teams have successfully reproduced the attack by executing a payload via their WHMCS add-on in communication with their API. Virtualizor denies this attack vector and has asked us to deny it as well to avoid “damaging” their brand image. The result is that the attacker did indeed go through Virtualizor via the WHMCS add-on.
And then today:
We will communicate exactly how to exploit the vulnerability to Virtualizor in a video so that they can ‘try’ to patch this type of attack.
Wow! Stay tuned, loyal readers, because this is about to get very interesting.
























Leave a Reply