Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

3/14/2012
03:57 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Microsoft Flaw Demonstrates Dangers Of Remote Desktop Access

Fear is that attackers will soon come up with exploits for targeted attacks, worms

Microsoft's Patch Tuesday warning of possible attacks emerging quickly for a vulnerability in its Remote Desktop Protocol (RDP) is a chilling reminder of the potential dangers of desktop remote-access tools commonly used by IT departments to handle from afar help-desk issues and by administrators to manage virtualized machines.

The sole "critical" vulnerability among the updates in Microsoft's batch of patches yesterday was for a flaw in Microsoft's implementation of RDP, which gives one user remote access to another's desktop. Microsoft strongly urged users to patch this one (CVE-2012-002 in MS12-020) as soon as possible, or to apply the FixIt temporary fix that was also issued among the updates. Other security organizations, such as SANS, and vendors echoed Microsoft's warning that this particular patch should be a priority this month.

"Although Remote Desktop Protocol, RDP, is not enabled on the default configuration for any version of Windows, Microsoft strongly recommends that all customers prioritize the MS12-020 security update this month, in order to ensure that systems are protected," a Microsoft spokesperson said. Microsoft says an attacker could reverse-engineer its new patch for the RDP bug in relatively short order, which raises the potential for exploits to be written for a targeted attack or for automatic-propagation worms that would let attacks quickly take over systems within corporate networks for botnets or other purposes.

That's a scary scenario, security experts say. "We saw this two months ago with Symantec's pcAnywhere" remote-desktop tool code leak," says Wolfgang Kandek, CTO at Qualys. "All of these remote-access tools are great for productivity, but when you set them up and look at who connects and how you can restrict that," it's just username and password, which is weak, Kandek says.

Remote-desktop access tools are popular among organizations with branch offices and users who work at home: Rather than the old days where the IT guy flew to the branch office to physically work on the user's machine, the tools allow IT and security teams to work on users' machines from their own desktops. And this feature is used for managing virtualized servers and machines, including Amazon's EC2.

This particular vulnerability with Microsoft's RDP is a preauthentication one, so an attacker could get into the machine without even using credentials. "It seems rather easy to exploit, which is why they are urging [customers] to patch this as quickly as possible," Kandek says.

SANS Internet Storm Center handler Lenny Zeltser recommended that users move their RDP "listeners" to non-standard ports, rather than TCP port 3389, where it traditionally sits. "Until you install the patch, consider moving your RDP listeners to non-standard ports," Zeltser said in a SANS ISC Diary post.

Microsoft yesterday also offered up the FixIt tool for the vulnerability that lets users enable the Network Level Authentication (NLA) feature in RDP. NLA would require the attacker to authenticate to the server before trying to run an exploit, and ISC's Seltzer also recommends checking out NLA as an option.

[Remote VPN connections are not necessarily as secure as you'd think -- how enterprises can get infected by far-flung users via their SSL VPNs. See VPN An Oft-Forgotten Attack Vector. ]

Leaving RDP open basically increases your attack surface, says Rainer Enders, CTO Americas at NCP Engineering. "If you have it running, you have an active connection that can be attacked," he says. "And the way it's used, an app can be used from any machine."

Jason Miller, manager of research and development for VMware, says RDP is commonly used to connect to virtualized machines. "Although Microsoft is stating that most machines do not have RDP enabled by default, I know of many organizations that use RDP to troubleshoot machines," Miller said in a blog post. "This Windows component comes even more into play with machines that are not physically located next to users, such as virtualized machines."

He worries that the vulnerability could be exploited as a worm: "This bulletin simply scares me when it comes to protecting an environment from future attacks. This vulnerability has the real potential to become victim to a worm outbreak if this vulnerability is not patched," he said. "Although this vulnerability may be difficult to exploit, I can assure you attackers will be working hard to create a valid attack against the vulnerability."

So how can you use remote desktop access safely? Qualys' Kandek recommends adding another security control to the picture, including firewalls or first requiring a VPN log-in.

"The security battlefield today is the access device," NCP's Enders adds. "Administrators need to pay more attention [to these devices]."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
MITRE Releases 2019 List of Top 25 Software Weaknesses
Kelly Sheridan, Staff Editor, Dark Reading,  9/17/2019
Preventing PTSD and Burnout for Cybersecurity Professionals
Craig Hinkley, CEO, WhiteHat Security,  9/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14821
PUBLISHED: 2019-09-19
An out-of-bounds access issue was found in the Linux kernel, all versions through 5.3, in the way Linux kernel's KVM hypervisor implements the Coalesced MMIO write operation. It operates on an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write indices 'ring->first' and 'ring->l...
CVE-2019-15032
PUBLISHED: 2019-09-19
Pydio 6.0.8 mishandles error reporting when a directory allows unauthenticated uploads, and the remote-upload option is used with the http://localhost:22 URL. The attacker can obtain sensitive information such as the name of the user who created that directory and other internal server information.
CVE-2019-15033
PUBLISHED: 2019-09-19
Pydio 6.0.8 allows Authenticated SSRF during a Remote Link Feature download. An attacker can specify an intranet address in the file parameter to index.php, when sending a file to a remote server, as demonstrated by the file=http%3A%2F%2F192.168.1.2 substring.
CVE-2019-16412
PUBLISHED: 2019-09-19
In goform/setSysTools on Tenda N301 wireless routers, attackers can trigger a device crash via a zero wanMTU value. (Prohibition of this zero value is only enforced within the GUI.)
CVE-2019-16510
PUBLISHED: 2019-09-19
libIEC61850 through 1.3.3 has a use-after-free in MmsServer_waitReady in mms/iso_mms/server/mms_server.c, as demonstrated by server_example_goose.