AboutContributeGitHub
Menu

BlueKeep (CVE-2019-0708)

BlueKeep was one of the first vulnerabilities since the WannaCry and NotPetya outbreaks to prompt public warnings from Microsoft, the U.S. NSA, and other national cybersecurity agencies about the risk of a self-propagating worm. It drove an unusual step by Microsoft: issuing patches for out-of-support systems such as Windows XP and Server 2003. The eventual public release of a working Metasploit exploit module also became a widely cited case study in coordinated vulnerability disclosure, patch-gap risk, and internet-wide scanning for unpatched RDP endpoints.

Background

CVE-2019-0708, popularly known as "BlueKeep," is a critical remote code execution vulnerability in Microsoft's Remote Desktop Services (formerly Terminal Services) on older versions of Windows, including Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows 7, and Windows Server 2008 and 2008 R2. The flaw is a use-after-free condition triggered when the Remote Desktop Protocol (RDP) server binds a special internal communication channel named "MS_T120" incorrectly, allowing an unauthenticated remote attacker to send specially crafted RDP requests that corrupt memory and execute arbitrary code with system-level privileges.

Discovery and Disclosure

The vulnerability was reported to Microsoft by the United Kingdom's National Cyber Security Centre (NCSC). Microsoft publicly disclosed and patched the flaw on May 14, 2019, as part of its regular Patch Tuesday release. Because the affected protocol required no user authentication and no user interaction to exploit, and because the flaw was assessed as "wormable" — capable of spreading automatically between vulnerable systems in a manner similar to the 2017 WannaCry ransomware outbreak, which itself exploited a different RDP/SMB-related weakness — Microsoft took the unusual step of also releasing patches for several operating systems that had already reached end of support, including Windows XP, Windows Server 2003, and Windows Vista.

Public Warnings

Following disclosure, Microsoft published a security blog post explicitly warning customers to patch immediately, drawing direct comparisons to WannaCry. On June 4, 2019, the U.S. National Security Agency (NSA) took the rare step of issuing its own advisory urging organizations to patch affected systems, disable Remote Desktop Services if not required, block the RDP port (TCP 3389) at the network perimeter, and enable Network Level Authentication (NLA) as a mitigating control. Numerous other national CERTs and agencies, including the UK's NCSC, issued similar warnings.

Exploit Development

In the months following disclosure, security researchers worked on proof-of-concept exploit code without releasing fully weaponized tools, citing concerns over a potential worm outbreak. Security firm Sophos published research demonstrating exploitability around July 2019, and researchers at organizations including McAfee and Check Point separately demonstrated working exploits. On September 6, 2019, the Metasploit Project publicly released an exploit module for BlueKeep, enabling remote code execution against vulnerable Windows 7 and Server 2008 R2 systems, though the initial module's reliability was limited and known to crash target systems.

Exploitation in the Wild

Mass scanning for internet-exposed, unpatched RDP endpoints began soon after disclosure, with hundreds of thousands of vulnerable systems identified by researchers at organizations such as the SANS Internet Storm Center and BinaryEdge. The first confirmed mass exploitation was reported around November 2, 2019, when researcher Kevin Beaumont and others observed BlueKeep being used in the wild, primarily to install cryptocurrency-mining malware on compromised hosts rather than to conduct a self-propagating worm attack of the scale initially feared.

Related Vulnerabilities and Legacy

In August 2019, Microsoft disclosed a related set of RDP vulnerabilities dubbed "DejaBlue" (including CVE-2019-1181 and CVE-2019-1182), which extended similar wormable remote-code-execution risk to newer Windows versions, including Windows 10 and Server 2019. BlueKeep is widely cited in cybersecurity education and industry retrospectives as a case study in patch-gap risk, the persistence of legacy internet-facing infrastructure, and the value of coordinated vulnerability disclosure between national security agencies and software vendors. It remains listed in the U.S. Cybersecurity and Infrastructure Security Agency's (CISA) Known Exploited Vulnerabilities catalog.

Timeline

  • 2019-05-14Microsoft publicly discloses CVE-2019-0708 ("BlueKeep") and releases patches, including for out-of-support systems such as Windows XP and Server 2003, as part of its May Patch Tuesday.
  • 2019-05-30Microsoft publishes a security blog post urging customers to patch, explicitly comparing the risk to the 2017 WannaCry outbreak.
  • 2019-06-04The U.S. National Security Agency (NSA) issues a rare public advisory urging organizations to patch systems against BlueKeep.
  • 2019-07Security firm Sophos publishes research demonstrating exploitability of the vulnerability.
  • 2019-08Microsoft discloses a related set of wormable RDP vulnerabilities, dubbed "DejaBlue," affecting newer Windows versions including Windows 10.
  • 2019-09-06The Metasploit Project publicly releases a working exploit module for BlueKeep.
  • 2019-11-02Researchers report the first confirmed mass-scale exploitation of BlueKeep in the wild, primarily to deploy cryptocurrency-mining malware.
BlueKeep (CVE-2019-0708)
Type
Vulnerability / Discovery
Era
2019
Key date
2019
Tags
rdp, windows, wormable, remote-code-execution, microsoft, patch-tuesday, critical-infrastructure
Created by Joas A Santos · Something wrong or want it removed? Open an issue.