Security Flaw Hits VAserv; Head of LxLabs Found Hanged
Keldrin_1 writes "The discovery of 24 security vulnerabilities may have contributed to the death of the chief of LxLabs. A flaw in the company's HyperVM software allowed data on 100,000 sites, all hosted by VAserv, to be destroyed. The HyperVM solution is popular with cheap web hosting services and the attacks are easy to reproduce, which could lead to further incidents."
I guess there's not much to say...
Just closed an account with VAserv last week for no particular reason.
I hardly ever do things for "no particular reason" so it must have been my spider sense.
Will this be a case of good bye reputation, or no publicity is bad publicity?
That's one way to dodge all those bug reports...
Skiffy is Spiffy, but Ort is tort.
You can't truly blame Milw0rm for a person being depressed and committing suicide.
However, reading their security notes on it, they did hear back from the developer...they simply declared that it didn't happen fast enough and decided unilaterally that the "Vendor appears uninterested".
I have very mixed feelings on security firms releasing exploits to the public just to try and get results. In my (admittedly limited) experience, more bad has come from releasing exploits publicly than good.
-JJS
Backup your own damn data. If you trust your webhoster to do it for you, you're a lost cause.
According to the article, there have been other suicides in the family a few years ago. Let's just discuss tech, and let the personal stay personal.
Had been posited for about 2-3 years now. It is actually amazing that this was such a brutal attack.
The dangers of these attacks had always been stealth related, because it is nearly impossible for the machine to SEE the vm manager. Which makes these things even more dangerous than rootkits.
My condolences to Mr. Ligesh's family.
http://timesofindia.indiatimes.com/Bangalore/Techie-hangs-himself-in-HSR-Layout-/articleshow/4633101.cms
Sounds like the guy needed some more help than he got to get to grips with his personal situation. Anyway ...
The flaws include SQL injection vulnerabilities and flaws that create a way for hackers to gain file access to files hosted on a vulnerable system.
There is no excuse for SQL Injection vulnerabilities these days. The problem is well known and publicised, the solutions are well documented. This is a problem that is solved by altering how you code, that results in neater code with less errors. If you can't use prepared/parameterised statements and insist on building SQL command strings out of user supplied data, then ... well, err, I can't say "you deserve to hang" in this case can I?
His sister and mother both committed suicide by hanging 5 years ago. He may have had a genetic propensity towards suicide.
Culturally, Indians have a very heavy emphasis on honor and responsibility. The failure of the software is only the outermost layer of true damage. Each of those compromised VMs is a failure to satisfy a customer at best, and a grave violation of the trust between vendor and customer.
When it comes to suicide, why hanging? It seems like a really hard way to go. Maybe the person wants to suffer to pay back his debts before death.
Hopefully the sites lost were those abandoned blogs, even better if they were active blogs.
The guys pic
http://i41.tinypic.com/zjdqgy.jpg
RIP
I think it is quite disturbing with all of the disrespectful comments on this article. I could Mod some of this, but not all of it. The guy obviously hit hard times with death of two family members by suicide and the tanking of his company. It is clear he had depression in his family and was not able to bear all of this hitting him. It is sickening that so many of you think it is a joke.
Just because you are wrong and I called you out on it doesn't mean I am a Troll.
That's like putting your mission critical servers in a garden shed with holes in the roof.
What??? It's not a cheap way to get my server water cooled???
Could this explain my high hardware failure?
I'm sure this guy was already unstable but can't help but believe that the attacks were what finally pushed him over the edge. Legally this would be difficult to prosecute as murder but morally those little script kiddies who so impressed with themselves should consider the unintended consequences of their actions. We are all responsible for our own actions (suicide) but should be equally concerned with how our actions affect others (hackers).
Many/most (cheapvps, fsckvps, etc.) are reselling VAserv stuff, so a lot have been hit hard.
If they're using HyperVM, stay the hell away.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
but I gotta respect this guy's dedication to the job. If we could get American CEO's to take this level of responsibility when their companies completely faceplant, the world would be a better place.
Support the EFF and Creative Commons. The war is coming, and they're supporting you...
Why don't you round them up, put identifying badges on them, and then try killing them yourse-
Oh wait.
Godwin's law, dammit.
Can you imagine if a Microsoft executive hung himself every time a vulnerability was discovered in Windows that led to data loss?
Request: Please no one post links to the VAserv status page. The last thing we need is to /. them right now. Customers have been emailed the URL and we are the only ones who really need to see it (plus it isn't very interesting).
VAserv have emailed customers to say they will be taken over by BlueSquare (where they do most of their hosting anyway). Probably the best option given the scale of the attack.
I've got one apparently deleted VPS and one still running. The whole situation is terribly frustrating. However I don't think the lack of information coming from VAserv is due to a lack of effort on their part.
is not appreciated by those who think they are immortal
ie, teenaged idiots
that the world is full of teenaged idiots (most of whom are not chronologically actual teenagers) should not surprise you or disappoint you
just a simple ugliness of life you need to learn to accept, like people who throw their garbage on the ground or talk loudly at movies, its another example of the tragedy of the commons
sure you could declare a high holy moral crusade against boorish insensitivity, but its like trying to stop the sun from rising and setting: a lot of people are ignorant assholes, status permanent, and even those you might actually be able to educate are quickly replaced by more morons
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Well, not exactly. There is a raging debate over whether this is an appropriate tactic, and this incident will go down in the security text books as an example of why the debate exists. Opposite your opinion is something like, "That's what publicity seeking sociopathic nerds, masquerading as [security folk] do."
There is a fundamental tension between wanting to know if a system you own is vulnerable to some defect, and wanting to keep the exploit code out of the hands of The Bad Guys(TM). In this case, however, it seems pretty clear that simply knowing the name of the product (not even the version) was enough, exploit code wasn't required (as it sometimes is when scanning large numbers of systems that might be at indeterminate patch levels, for example).
There are quite a few actions one could take between "notify the vendor" and "release exploit code" which appear to have been skipped. That's irresponsible, not, "what security folks do".
Frankly, I don't understand how organizations or consultants who do this kind of thing manage to stay in business. If you were a big company with a bunch of interlocking IT systems and limited resources, would you hire someone who had a track record of publishing exploit code before patches were available? Suppose this consultant found some issues, which your organization couldn't respond to as quickly as you would like? Does that consultant become a risk to you now, simply because you didn't fix something in a manner timely enough to suit them? How do you know they wouldn't publish details of your vulnerabilities, because some snot nose punk with an inflated sense of self-righteousness thought you were ignoring him?
I don't operate that way, and neither do any of the fine security consultants who work for me or with me. I work discretely with my clients until they get their problems fixed. That sometimes means doing a lot more work than *should* be required to get the attention of a vendor. However, it has never yet meant publishing exploit code prior to patch availability.
If you mod me down, I shall become more powerful than you could possibly imagine.
Some rather unpleasant comments coming off of you lot.
The poor chap sounds like he'd had a bad decade, and this just topped it off.
When your business collapses overnight (which is what happened here), you're facing god knows how many lawsuits (which is what would have happened here) and the people you'd turn to for support are dead... Well, I'd imagine what follows are some rather sobering thoughts.
My heart goes out to his remaining family, and those of you modded "Funny" should go gargle some engine coolant.
You feel sleepy. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.
I think many people may have been confused as to what they meant by data back up. There are back ups you need in case you delete all of your data accidentally, or want to go back to a previous revision. Those would be back ups due to web host user screw ups. This wasn't a web host user screw up, it was a web host screw up. The users probably didn't consider it a likely occurrence, and may have believed that the web host should be able to fix a problem that they allowed due to their negligence.
Well.. maybe. Or Maybe not. But Definitely not sort of.
five years ago, not a few months.
Summary from http://www.milw0rm.com/exploits/8880 seems pretty serious but quite difficult to fix all of them in 2 weeks.
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
2 weeks have passed since the initial notification. Vendor appears
uninterested.
ISSUE 1 - uid/gid reuse
ISSUE 2 - unprivileged port use
ISSUE 3 - default passwords
ISSUE 4 - useradd string in the process list
ISSUE 5 - XSS
ISSUE 6 - remotely create partially user controlled file names
and directories. Locally append uncontrolled data to
any file
ISSUE 7 - local users can take control of any file or directory
ISSUE 8 - local users can take control of any file or directory
ISSUE 9 - local users can overwrite any file on the box
ISSUE 10 - yet another symlink attack for local users
ISSUE 11 - metachar injection, local command execution as root
ISSUE 12 - web stats world readable password hashes
ISSUE 13 - local users can overwrite any file on the box
ISSUE 14 - metachar injection, local command execution as root
ISSUE 15 - remotely block any - or every - IP addr in hosts.deny
ISSUE 16 - remote CPU and mem usage DoS
ISSUE 17 - local users can truncate and control any file
ISSUE 18 - just 2 more symlinks to own any file on the box
ISSUE 19 - file manager, view and edit any file
ISSUE 20 - file manager PT II
ISSUE 21 - file manager PT III
ISSUE 22 - local user symlink attack
ISSUE 23 - local user symlink attack (last one)
ISSUE 24 - sql injection in the "Forgot Password" form
Ian
very sad story, very sorry to hear about your brother.
"While suicide should never be celebrated, there's a certain honor in doing it as a result of professional failure."
It can be the ultimate apology. While your post will be modded Troll, other societies see things differently. Seppuku, anyone?
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
Yes, I meant hanged. Sorry, english is not my first language.
I've known relations who have opted for suicide, or who have been hospitalized to prevent them. None as close as immediate family, so I can't begin to understand the pain, but in my own way I can dimly see.
One thing that makes this sort of thing doubly painful is that the sorts of minds that can consider suicide a real possibility are often very very close (and sometimes the same) as the minds that are brilliant.
We talk of genius and madness being a razor's edge away from each other, not because it is poetic but because it's true. But you don't have to be a genius to be that razor's edge away from self-destruction. You only have to have a similar biochemistry and/or neurology. There are dozens of conditions linked both to creative talent and self-harm.
Of course, not all suicides are for that reason. Utter despair (which I guess is still biochemical, but it's not a permanent condition) is another reason. There are doubtless many others.
I guess this sort of intellectualizing of suicide is my own way of dealing with the pain I have, for all that it's nothing compared to that of those close to such victims. So long as I intellectualize it, I can imagine that there will someday be solutions which help such people and prevent such tragedies happening.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
There is only so much due diligence you can do if their claims are not true.
Phillip.
Property for sale in Nice, France
I disagree; it should logically follow that a company should have some kind of disaster recovery plan other than "Oops, it's all gone, but how about a few months of free service?" If that's what customers want and I could get away with then damn, I've been wasting time and money keeping disaster recovery backups offsite. I'm not talking about backups like customers accidentally deleting files, but loss of service due to events beyond your control.
Yes, you should have copies of your own stuff, the more the better. For vahost even if the "oh crap" backup was a week old that would have been better than the total loss they're selling as "not our fault we dun got hacked".
this is my sig
It doesn't matter; the point of a disaster recovery backup (or plan) is not to protect your clients against accidentally deleting files, but to protect you (and them) from events that are completely outside of your control.
Who says they didn't have a disaster recovery plan? The issue at hand for many of the sites that have no backups at all for their data is because they chose a plan that explicitly stated that it was unmanaged and that VAserv wasn't going to back up the data for you.