Heartbleed: What the OpenSSL Bug Means for Your Business

From the archive: this article was written in 2014 and reflects the technology and threats of that time. For current advice, see our latest articles or ask us directly.

The little padlock in your browser's address bar is supposed to mean "this connection is private." Last week we learned that on a huge number of websites, that padlock had a hidden flaw for about two years. The bug has a catchy name — Heartbleed — and a logo, which is unusual for a security problem. The attention is deserved.

Since the news broke on April 7, we have fielded plenty of versions of the same question: "Do I need to change all my passwords right now?" The short answer is yes, eventually, but timing matters. Here is what happened and what a small business should actually do about it.

What Heartbleed is, in plain English

Much of the secure internet runs on a free, open-source toolkit called OpenSSL. It is the engine behind the padlock on a very large share of websites, and it is built into countless other products. OpenSSL includes a feature called "heartbeat," which lets two computers check that a secure connection is still alive. One side says, in effect, "Here is a small message; send it back to me so I know you are there."

The flaw was that OpenSSL did not check whether the message was really as long as the sender claimed. An attacker could send a tiny message while claiming it was large, and the server would dutifully send back the message plus whatever happened to be sitting next to it in memory — up to about 64 kilobytes at a time. Repeat that over and over, and you can collect chunks of whatever the server was working on.

What might be in that memory? Potentially usernames and passwords of people who recently logged in, session cookies, private messages, and in some cases the server's own secret encryption keys. Worse, the attack left no obvious trace in normal logs, so most sites cannot tell whether they were targeted.

Heartbleed did not break encryption. It let someone reach past it and read what the server was holding in its hands.

Why you should not rush to change every password today

This part surprises people. If you change your password on a site that has not yet fixed the bug, your new password is just as exposed as the old one. The right order is:

  1. Wait until the site has confirmed it has patched OpenSSL.
  2. Ideally, confirm it has also replaced its security certificate.
  3. Then change your password.

Many large services have published statements about whether they were affected and whether users should change passwords. Several news outlets and security firms are maintaining lists. Check before you act, and prioritize the accounts that matter most: email, banking, payroll, and anything that holds customer data.

This is also a good moment to break the habit of reusing one password everywhere. If a password was exposed on one site and you used it on five others, all five are at risk. We will have more to say on managing passwords sensibly in a future post.

It is not just websites

Here is the part that matters most for a business, and that gets less attention in the headlines. OpenSSL is not only on web servers. It is built into a wide range of equipment that you probably do not think of as "a server":

  • Firewalls and VPN appliances. Several major networking vendors have confirmed that some of their products are affected and are releasing updates. A vulnerable VPN device is especially concerning, because it guards the front door to your network.
  • Network storage (NAS) devices with a web management page.
  • Email servers and web-based email access hosted in-house.
  • Printers, phone systems, and security camera recorders that offer secure web logins.
  • Linux servers running recent versions of common distributions.

Not every device is vulnerable — only products using the affected OpenSSL versions (1.0.1 through 1.0.1f), and plenty of equipment uses older or different code. Windows servers running Microsoft's own web server generally were not affected, because Microsoft uses its own encryption library. But you will not know about your specific gear until someone checks.

What a proper fix looks like

For systems you control, fixing Heartbleed takes more than one step:

  • Update OpenSSL or apply the vendor's firmware update (OpenSSL 1.0.1g fixes the bug).
  • Replace the security certificate and generate new private keys, since the old ones may have leaked.
  • Revoke the old certificate.
  • Reset passwords for administrator accounts and, where appropriate, ask users to change theirs.
  • Log out active sessions so any stolen session cookies stop working.

Patching alone closes the hole but leaves any keys that were already taken still usable by whoever took them.

What to do now

  1. Make a list of your internet-facing equipment: firewall, VPN, remote access, email, NAS, any in-house web applications.
  2. Check each vendor's Heartbleed advisory, and apply updates where needed.
  3. For affected systems, replace certificates and reset administrator passwords.
  4. Watch for confirmation from your key online services, then change those passwords.
  5. Turn on two-step verification wherever it is offered.
  6. Stop reusing passwords across accounts.

Heartbleed is a reminder that security depends on components most of us never see, buried inside the devices we rely on every day. Keeping track of that equipment — and keeping it patched — is a big part of what we do in server administration for businesses around Tampa Bay. If you are not sure whether your firewall, VPN, or storage device is affected, send us a note at info@pinellasit.com and we will help you check.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment