Forum Moderators: phranque
A large internet service provider said data for as many as 100,000 websites was destroyed by attackers who targeted a zero-day vulnerability in a widely-used virtualization application.
Technicians at UK-based Vaserv.com were still scrambling to recover data on Monday evening UK time, more than 24 hours after unknown hackers were able to gain root access to the company's system, Rus Foster, the company's director told The Register. He said the attackers were able to penetrate his servers by exploiting a critical vulnerability in HyperVM, a virtualization application made by a company called LXLabs.
It appears the hackers got root access and did a
rm -rf. The sites were on unmanaged, virtualized VPSes, so backups were in many cases the responsibility of the clients. HyperVM is a web based management application than sits on top of Xen/Virtuozzo, not an actual virtualization application itself. The hack was a SQL injection via the web interface, known to the product developers but currently unpatched. HyperVM is used by many different VPS providers, who may also be vulnerable to a similar hack.
That's why they call it "work".
[h-online.com...]
I'm not going to link to malicious code, but the timeline the anonymous hacker left as a comment:
# Timeline :
#
# 05/21/2009 - sent initial email to vendor with a link to a private
# resource for viewing various kloxo hiab575
# vulnerability info
#
# 05/23/2009 - received the following: "Thanks for the info. I will
# review this and let you know." (no signature)
#
# 05/30/2009 - sent an email asking if there were any updates
#
# 06/01/2009 - received the following: "Sorry for the delay. I am
# currently looking into this, and will reply in a couple
# of hours time." (no signature)
#
# 06/04/2009 - nothing heard from vendor, and the private resource
# containing the vulnerability info still does not
# appear to have been accessed
The apparent suicide of the author of course makes it even far more tragic.
Those affected by the outage can find status updates at
[66.71.245.2...] (I'd guess this is a temporary resource, but it;s been there quite a bit)
This exploit must have been around for some time and the hosting company just wasn't staying current with news as well as the Company that prouced the software.
All this could have been avoided with proper homework and staying up with current news assoicated with their business.
Very sad that this pushed a man to take his life.
From reading more into this it seems this has been a know exploit for some time and how to excute the exploit has been available and published on the web weeks before this happned.
Wehost should have taken protective measures. They had to have know of this issue and didn't take the steps to protect.
This could and most likely will lead to some legal action against them.
It is rare that hacks of this nature are so destructive - often the aim of a hack is to introduce rootkits or backdoors and profit from the stored confidential information, rather than the chaos caused by a full delete.
It is also a reminder that virtualization and VPS solutions are not necessarily as secure as you'd think. It is possible for a hacker to exit the virtualized environment and access other instances or the machine's real root.
Sad that my point had to be made by someone whacking entire servers.
This exploit must have been around for some time and the hosting company just wasn't staying current with news as well as the Company that prouced the software.
Read the timeline above, doesn't sound like it was known for very long.
Having been a host, we once had a RedHat vulnerability being actively exploited and there was nothing we could do to stop it until RedHat patched it, and they said it would take 7 days before the patch would be available. The most we could do was have a stack of clean drives ready and each time another server was breached we swapped the OS drive and it was back online, and that went on for 7 days.
Quite annoying but luckily nobody wiped the drives, they just installed rootkits and went away which is what the clean OS drive swap got rid of, over and over again.
It is also a reminder that virtualization and VPS solutions are not necessarily as secure as you'd think. It is possible for a hacker to exit the virtualized environment and access other instances or the machine's real root.
A lot of that depends on how you configure the virtualized environment. And the same could be said about a great many web facing apps and utils (SQL anyone?)
The big problem is that virtualization is fairly new stuff. The people running it have little experience with it and there's a lot of new products on the market that haven't been thoroughly tested.
The power of virtualized environments is fantastic. You can clone VMs on the fly, distribute them across an array for load balancing. Depending on the technology and infrastructure you use, you can spin up new machines in seconds - compare that to how long it takes to integrate a new linux box into an existing cluster.
The downside...
There's a lot of security issues, both popularly known ones and fairly obscure ones.
And there are so many players competing for dollars now it isn't even funny. A few years ago, it was VMware or bust. Now... Sun, IBM, MS, all have virtualization products. And that's just the big names. Small virtualization outfits are a dime a dozen.
It's a market that's going to grow, and expect it to become a larger presence in the hosting sphere. But there's going to be some serious growing pains.
This was the extent of their message on the subject:
Hi
I'm afraid that there are no backups of this due to he hacker attack
Keep looking for the "sorry" all you like, it's not there...