User account

New OpenStack KVM VPS locations: Dallas and Fremont

Our new KVM VPS’es platform, powered by Fleio and OpenStack, is now available in Dallas and Fremont.

You get the same benefits as in the previously opened locations (Amsterdam and Bucharest):

  • blazing fast full SSD local storage
  • brand new powerful Intel Xeon powered servers
  • generous traffic included
  • our fast and friendly 24/7 support for network, hardware and Fleio self-service portal

The virtual machines cost starts at one cent and half per hour for 2GB of RAM.

And some useful add-ons are available for the virtual machines:

  • Windows license for less than a cent per hour
  • affordable cPanel/WHM and DirectAdmin licenses
  • affordable extra IPv4 addresses

The new platform will soon be available in London too.

 

Double memory

We’ve doubled the amount of guaranteed memory for all virtual machines. This is already active for existing machines and no restart is required. We have also removed the “burst memory”, which is now guaranteed.

All other package characteristics have remained the same, including price.

If you happen to encounter any issue caused by the upgrade open a support ticket.

 

Heartbleed OpenSSL Vulnerability

On April 7, 2014  CVE-2014-0160 vulnerability, also known as “Heartbleed”, was released that could allow attackers to view sensitive information in a server’s memory such as secret keys and passwords. Given the severity of this problem, IntoVPS has taken the necessary steps to secure our web sites and keep our customers’ information safe from potential attacks.

A tool has been published that allows administrators to test the vulnerability of their system. If your site has an SSL certificate, go to the Heartbleed test page, enter your website URL, and run the vulnerability test.

If you are vulnerable please update openssl as soon as possible and restart your web server.

On Ubuntu/Debian:
sudo apt-get update
sudo apt-get upgrade
sudo /etc/init.d/apache2 restart

On Centos:
yum -y install openssl
/etc/init.d/httpd restart

Also Ars is reporting that a bot has been exploiting heartbleed in the wild since at least nov 2013. Therefore, we strongly suggest to reissue all the affected SSL certificates.

 

Kloxo zero-day exploit

Today we started to see our packet counter monitors triggering all over the place. At a closer look we’ve noticed a common pattern: scripts flooding from customers’ virtual machines running Kloxo.

A zero-day exploit has been identified in Kloxo control panel today. Here’s a discussion related to this.

We decided a few hours ago to proactively fix this inside ALL machines running Kloxo:

  • identify offending script that was uploaded and chmod 0 the directory
  • stop the kloxo daemon
  • email each and every (!) customer about this exploit and explaining the actions we took

Ionut and Ovidiu have just completed these steps and we managed to stop this pest, for now.

We don’t normally run commands inside customers’ virtual machines, but we decided that it’s the best action we can take in the interest of everyone involved. And by everyone, I mean everyone: compromised machine’s owner, other IntoVPS customers, IntoVPS employees and stakeholders, internet community.

Here’s the email we’ve sent:

Subject: IntoVPS – Kloxo installation compromised for server

Hello,

You are receiving this notification because you are running Kloxo panel management on your VPS named XXXXXXX.

It seems that Kloxo installations are compromised with a randomly-named PHP file placed into /home/kloxo/httpd/default/, which is the ‘default’ site accessible by IP address and that kloxo appear to be spawning a large number of httpd processes. Further investigation shows they’re all sending out volumes of traffic as part of a ddos.

Here is an example of a compromised file uploaded in /home/kloxo/httpd/default: http://disclosed.info/?7c12a1a4560b7664#5fpnfdknf4EfBcGqLjeV9/vAY1RXEKkLC3+fqm16c6E=

At this moment there isn’t any fix published for Kloxo and as a workaround for this particular issue, we are going to change the permission of that folder to 0 with the following command:

chmod 0 /home/kloxo/httpd/default/
chmod 0 /home/admin/*/cgi-bin

Also is it better for now to stop kloxo daemon until a proper fix is released.

/etc/init.d/kloxo stop

We also noticed the same particular file being uploaded in the cgi-bin folders of the website managed by admin users. I strongly advice to check this as well and remove or change permission of those files that contains the same patern as soon as possible.

If you have any questions, please let us know.

Best regards,
IntoVPS Support