Patched: OpenSSL Heartbleed Vulnerability CVE-2014-0160

heartbleedThis morning we deployed an update to the OpenSSL software packages on our shared and customer servers to address a critical vulnerability. The vulnerability, dubbed “heartbleed”, is the result of improper data validation (bounds check) within a “heartbeat” feature of the OpenSSL TLS implementation.

Because of this vulnerability, it is possible that a portion of active memory can be disclosed to connecting clients, which can leak sensitive information. Ultimately, this may lead to the disclosure of transaction or customer-identifiable information, which undermines the very purpose of SSL implementations for our customers and the Internet community at large.

Although we make every effort to schedule updates and maintenance, the critical nature of this vulnerability prompted immediate action. We’re working hard to protect our customers and want to thank you for your understanding.

What is the status of my SSL certificates?
Our position is that regenerating/reissuing SSL certificates is not explicitly required and doing so would be out of an abundance of caution. Although the heartbleed vulnerability had the very real possibility to disclose the server-side private key for an SSL certificate, the ability to capture an entire SSL private key required more than just a passing interest in a specific web site. An attacker would need to conduct a targeted effort to dump thousands of memory captures using the vulnerability and piece together an SSL private certificate, a non-trivial task.

Further, we have no indications at this time of any large scale attempts to compromise SSL private keys on our customer web sites, servers or network at large. We will continue to monitor our servers and networks with vigilance and if at any time we have indications that this position needs to change, we will update our customers accordingly.

If you have any questions or concerns regarding this or other issues, please get in touch and we’ll get back to you as soon as possible.

Vulnerability Scope:
For customers that are currently running cPanel/WHM, the OpenSSL update will apply within the next 24h through daily automatic updates. To verify that the update has applied or to proactively apply it, please find details below. It is important to note, that once the OpenSSL update has been applied, Apache and/or Nginx must be restarted to ensure that the vulnerability is properly closed.

Check the current OpenSSL Version:
# rpm -q openssl

The patched version of OpenSSL for CentOS 6 is openssl-1.0.1e-16.el6_5.7.x86_64.
The version of OpenSSL provided in CentOS 5.10 (openssl-0.9.8e-27.el5_10.1) is NOT vulnerable.
The version of OpenSSL provided in CentOS 6.5 (openssl-1.0.1e-16.el6_5.4) WAS vulnerable.

If you find that you are running any version other than ‘openssl-0.9.8e-27.el5_10.1′ or ‘openssl-1.0.1e-16.el6_5.7.x86_64′ then you should immediately update the OpenSSL packages:
# yum update -y openssl 
# /etc/init.d/httpd stop
# /etc/init.d/httpd start

Although we have made every effort to access and update customer systems, this may not always be possible in cases where customers may have restricted access to systems and/or are using operating systems other than RHEL/CentOS. As such, we encourage all Cloud VPS, Hybrid and Dedicated customers to verify that this vulnerability is patched with an updated OpenSSL package.

Additional update information:

Debian Wheezy, Jessie, Sid
# apt-get upgrade openssl

Ubuntu 12.04, 12.10, 13.10
# apt-get upgrade openssl

RHEL/CentOS 6.5
# yum update openssl

CentOS 5.10, OpenSSL 0.9.8 is NOT vulnerable

Vulnerability Details:

Proof of Concept Test:

Leave a comment

Shared servers maintenance – January 24th, 12PM EST

On Friday, January 24th 12PM EST, we will be conducting maintenance on three of our servers. These servers are:

This maintenance will include a migration of these servers to a new physical host. Please note that these migrations will cause a performance degradation on each server while data is being migrated, and may possibly result in 30 – 60 minutes of downtime per server.

Once these servers are migrated, customers should see improved performance. Thanks for your patience as we improve your hosting experience!

Leave a comment

SEO Web Hosting Newsletter December 2013

Welcome back to the SEOWebHosting Newsletter! 

We hope you’ve been having a great holiday. Many thanks for hosting with us! We can’t wait to assist you through 2014 and beyond!

Need assistance? Call 1-877-283-2614, or email us anytime!

What’s New?

Get 3 great SEO Web Hosting products for 1 low price.

Get a starter dedicated server, 15 IPs, and a Managed SEO plan for only $250 a month! Sale ends Monday January 6! 

Offer good for monthly pricing only. Discount added in cart. Click here to sign up! 

Important ICANN Announcement – Please Read!

Please read this important announcement from ICANN carefully, as it details new regulations and procedures for their Registar Accreditation Agreement.

Click here for the details.

Join The SEO Web Hosting Affiliate Program!

Earn great commissions by recommending any of our services! It’s free to sign up, and you don’t have to be a customer to join! Learn more here.

The SEO Web Hosting Team

Leave a comment

Important: ICANN Registrar Accreditation Agreement Changes


SEO Web Hosting Customers:

Please read this important announcement carefully!  The following post details new regulations and procedures for ICANN’s Registrar Accreditation Agreement:


Starting in January, the registrant contact will need to be validated upon the purchase or transfer of a domain name or if the registrant’s first name or last name has been modified.

Should any of these occur, OpenSRS , our registrar, will send an email requiring an affirmative response from the registrant. Failing to receive an affirmative response from the registrant within 15 days will result in the suspension of the name. This means that the domain (and any related services) will be offline.

If a registrant has already validated their contact information, this process will not be initiated.

The same validation process will take place if a WHOIS Data Reminder Policy (WDRP) notice, 30 day expiration notice or 5 day expiration notice bounces. It is extremely important to ensure the WHOIS data that you provide for your domain is correct.


ICANN now requires that we  list the following new pieces of information on your website:

• ICANN’s Registrant’s Benefits and Responsibilities

• ICANN’s site for registrant education

We hope that these changes in ICANN policy will have little effect on the ease in which you are able to order domain registrations or transfers. Please contact our billing department with any questions or concerns.

Leave a comment