@Jonathan Zahedieh
Jonathan,
You wrote:
"The researcher than found the vulnerabilities in the only gave the developer 2/3 weeks to fix it, looks like to me that he got peed off and released them to the public because lack of response."
I'd like to clarify this. First, I did not give the developer "2/3 weeks to fix" the issues. In fact, I did not give any timeline at all. What I did is what the advisory says. Had the vendor looked at the issues (which was not done) and requested some time to address them, of course, I would have given any amount of time requested before going public with the information.
Second, what it looks like to you and what really happened are 2 different things. I did not release the information out of anger with anyone. It was released so that customers, both current and potential, would be aware of the issues. It is not the job of the person who spends their time finding and documenting the bugs to babysit a vendor, plain and simple.
Third, as it stands, there is nothing whatsoever that definitively connects the current situation with the afflicted webhost with the information that was made publicly available. I audited Kloxo. As I understand it, and do correct me if I'm wrong, but they believe the issue was with HyperVM. I did not find out until later than HyperVM and Kloxo (formerly LxAdmin) share some of the same features/code.
Finally, lxlabs/kloxo/hypervm has been getting hacked for a while now, well before I ever published anything. Read their forums and you will see.