Metasploit published a public exploit for BlueKeep, the exploit module targets 64-bit versions of Windows 7 and Windows 2008 R2.
The Bluekeep is a wormable critical RCE vulnerability in Remote desktop services that let hackers access the vulnerable machine without authentication.
Successful exploitation of the vulnerability allows a remote attacker to run arbitrary code on the target system and can create a user account with elevated privileges.
Exploit Module for BlueKeep
The exploit module is currently based on manual targeting. By default, the exploit detects whether the operating system version and check are whether it is vulnerable to BlueKeep.
To exploit further, the user needs to manually specifies the target details and if the “the module is interrupted during exploitation, or if the incorrect target is specified, the target will crash with a bluescreen.”
The exploit developed based on the proof-of-concept code provided by the Metasploit contributor @zerosum0x0.
To use the current exploit, users need to provide details about Windows kernel memory for successful exploitation, Brent Cook said that limitation will be removed in the future. Exploit available from GitHub.
How to Check for Vulnerability
- To start the Metasploit Framework
- To Use Exploit
- Set Target
set RHOSTS to target hosts (x64 Windows 7 or 2008 R2)
- Set Payload
set PAYLOAD and associated options as desired
- Target details for second level of recon
set TARGET to a more specific target based on your environment
- Verify that you get a shell
- Verify the target does not crash
“As with many Metasploit exploits whose utility has endured over the years, we expect to continue refining the BlueKeep exploit over time.”
Malicious RDP Activity
Rapid 7 observed an uptick in malicious RDP activity, since the publication of Bluekeep vulnerability.
Microsoft urged users to update the patched Warmable BlueKeep Remote desktop protocol vulnerability due to the seriousness of this flaw let the hackers perform WannaCry level Attack.
Patches issued by Microsoft on May 14 and the vulnerability can be tracked as CVE-2019-0708.