BlueKeep: Patch Your Older Windows Machines Now

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

When Microsoft releases a security update for Windows XP, pay attention. XP support ended in 2014, and Microsoft almost never goes back to patch a retired system. Last Tuesday, it did exactly that. The reason is a vulnerability nicknamed BlueKeep, and it is one of the more serious Windows flaws we have seen in a couple of years.

The good news: there is a fix, it is free, and applying it is straightforward. The bad news: plenty of small business networks are full of the exact older machines this flaw affects. Here is what you need to know, in plain English.

What BlueKeep is

BlueKeep, officially tracked as CVE-2019-0708, is a flaw in Remote Desktop Services, the part of Windows that lets someone connect to and control a computer over the network using Remote Desktop (often called RDP). Microsoft disclosed and patched it on May 14, 2019.

The flaw lets an attacker send specially crafted traffic to a vulnerable computer's Remote Desktop service and run their own code on it. No password is required. Nobody has to click a link or open an attachment. If the machine is reachable and unpatched, that is enough.

The affected versions are the older ones:

  • Windows 7
  • Windows Server 2008 and Windows Server 2008 R2
  • Windows XP and Windows Server 2003 (both long out of support, which is why the special patch is notable)

Windows 8, Windows 10, and newer server versions are not affected by this particular flaw.

Why "wormable" is the scary word

Microsoft described BlueKeep as "wormable." That means malware using it could spread on its own from one vulnerable computer to the next, without any human help, the same way the WannaCry ransomware tore through hospitals, factories, and offices around the world in 2017.

With a wormable flaw, one infected machine on your network can become a launching pad to every other unpatched machine it can reach. For a small office where the front desk PC, the owner's desktop, and the old server in the closet all run Windows 7 or Server 2008 R2, that is a fast path from "one problem" to "everything is down."

As of this writing, there are no widely reported attacks using BlueKeep in the wild. That is exactly why now is the time to act. Security researchers expect working attack code to appear, and once it does, automated scanning of the internet for vulnerable systems tends to follow quickly.

The bigger lesson: never expose Remote Desktop to the internet

BlueKeep is especially dangerous for any computer that has Remote Desktop open directly to the internet. We still see this more often than we would like: someone set up port forwarding years ago so the owner could log in to the office server from home, and it has been quietly sitting there ever since.

Even before BlueKeep, internet-facing Remote Desktop was one of the most common ways criminals broke into small businesses. Attackers constantly scan for it and hammer it with password guesses. A patch fixes this specific flaw, but it does not fix the underlying problem of leaving the front door visible to the whole world.

Patching closes this hole. Taking Remote Desktop off the open internet closes the next one before anyone finds it.

If people need to reach office computers remotely, there are safer ways to do it: a VPN that requires its own login, a Remote Desktop Gateway, or a reputable remote access tool with multi-factor authentication. Any of these beats a bare Remote Desktop port facing the internet.

Why older machines keep causing these problems

BlueKeep is a preview of what is coming. Windows 7 and Server 2008 R2 reach end of support on January 14, 2020. Microsoft made an exception for XP this time because the flaw is so severe, but you cannot plan your security around exceptions. After next January, flaws like this one will simply stay open on those systems unless you are paying for extended updates.

If you have not started planning your move off Windows 7 and Server 2008, BlueKeep is a good nudge to get going.

What to do now

  1. Find every affected machine. Make a list of any computer or server running Windows 7, XP, Server 2003, Server 2008, or Server 2008 R2. Include the forgotten ones: the PC attached to lab equipment, the old server nobody wants to touch.
  2. Apply the May 2019 security updates. For supported systems, they arrive through Windows Update. For XP and Server 2003, Microsoft published the fix separately through its update catalog.
  3. Check for Remote Desktop exposed to the internet. Review your firewall and router for any rule forwarding port 3389 (the default Remote Desktop port) or a custom port to an inside machine. Close it.
  4. Turn off Remote Desktop where it is not needed. Many workstations have it enabled for no good reason.
  5. Enable Network Level Authentication. On systems that need Remote Desktop, this setting requires a valid login before the vulnerable part of the service is reached. It is a partial safeguard, not a replacement for patching.
  6. Plan replacements. Put your remaining Windows 7 and Server 2008 systems on a schedule to be upgraded or replaced before January 2020.

The bottom line

BlueKeep is serious, but it is also very fixable. Patch every affected machine, get Remote Desktop off the open internet, and use this as the push to retire systems that are about to lose support anyway. Keeping servers patched and remote access locked down is a core part of our server administration service. If you are not sure whether your network is exposed, email us at info@pinellasit.com and we will help you find out.

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