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.

Endpoint

8/13/2019
04:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

Microsoft Patches Wormable RCE Vulns in Remote Desktop Services

Similar to the now-patched 'BlueKeep' vulnerability, two flaws fixed today could let malware spread across vulnerable computers.

Microsoft today released 93 fixes and two advisories as part of its monthly Patch Tuesday update. Of these, 64 were categorized as Important in severity and 29 were ranked Critical.

Patching priority should be given to two "wormable" remote code execution (RCE) vulnerabilities that could allow future malware to spread across vulnerable machines without user interaction.

CVE-2019-1181 and CVE-2019-1182 affect Windows 8.1, Windows 7 SP1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, and all supported versions of Windows 10, including server versions. They do not affect Windows XP, Windows Server 2008, Windows Server 2008, or the Remote Desktop Protocol (RDP) itself. Like the BlueKeep RDP vulnerability patched this year, both could let an attacker remotely install and spread malware.

The vulnerabilities exist in Remote Desktop Services, formerly known as Terminal Services, when an unauthenticated attacker connects to a target system using RDP and sends specially crafted requests. Because they don't require authentication or user interaction, an attacker could install programs; view, edit, or delete data; or create new accounts with full user rights.

To exploit CVE-2019-1181 and CVE-2019-1182, an attacker would have to use RDP to send a specially crafted request to the target system's RDS. Today's update corrects how Remote Desktop Services handles connection requests. Neither bug has been seen in the wild.

"These vulnerabilities were discovered by Microsoft during hardening of Remote Desktop Services as part of our continual focus on strengthening the security of our products," writes Simon Pope, director of incident response for Microsoft's Security Response Center. "At this time, we have no evidence that these vulnerabilities were known to any third party."

Pope also points to a "partial mitigation" on affected systems with Network Level Authentication (NLA) enabled. Because NLA requires authentication before the flaw can be exploited, these systems are protected from wormable malware, he says. However, they are still vulnerable to RCE if attackers possess valid credentials they can use to authenticate.

Two additional vulnerabilities patched today, CVE-2019-1222 and CVE-2019-1226, are also Critical RCE bugs in RDS but, unlike the previously mentioned bugs, they're not wormable.

Those aside, patches issued today address bugs in Windows, Edge, Internet Explorer, Microsoft Office, Microsoft Office Services and Web Apps, ChakraCore, Azure DevOps Server, Visual Studio, Online Services, and Microsoft Dynamics. None were publicly known or under attack.

Another vulnerability worth noting is CVE-2019-1201, a Critical RCE bug in Microsoft Word resulting from improper handling of objects in memory. An attacker could exploit this by creating a specially crafted Word file and convincing a victim to open it, either by attaching it to an email or hosting it on a malicious website. Outlook's Reading/Preview Pane is an attack vector, meaning victims wouldn't have to open an attachment to be exploited; they could simply view the email. If successful, an attacker could achieve the same permissions a target user has on the system.

It was a big month for patching, especially RCE vulnerabilities: Microsoft also fixed RCE bugs in the Chakra Scripting Engine, Microsoft Graphics, Hyper-V, Outlook, Word, the Windows DHCP client, Scripting Engine, and the VBScript Engine.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/15/2019 | 12:55:10 PM
Re: We talked about this before

Yes, we do the same thing but we do it at the router or firewall where the port on the outside is 3288 which is redirected to 3389, but we also limit who can access that port as well (ACLs that limit our local offices or we use a jump host with login credentials, but a valid point you made earlier.

Todd
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
8/15/2019 | 9:55:41 AM
Re: We talked about this before
Port 3389 - also a known problem and I have always disabled that and moved TCP/IP to another available port whenever possible.  
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/14/2019 | 5:12:10 PM
We talked about this before

The vulnerabilities exist in Remote Desktop Services, formerly known as Terminal Services, when an unauthenticated attacker connects to a target system using RDP and sends specially crafted requests.

I think there was a similar article you wrote where we talking about the same issue with RDP (not sure) but it seems the underlying thread is that users who have access to RDP, it is not being authenticated. At somepoint if we don't have controls in place, individuals or nation-states are going to breach that system. I would look at the following items:
  • Add IP address range to only allow internal or external site connections
  • The section of the image where it says "Remote IP Address", select  "These IP Addressess" | "Predefined set of Computers" | Select "LocalSubnet" and if there is a range of external addresses, then add as needed
  • Next go to Start | Run | Type "sysdm.cpl" | Select the Tab "Remote", and make your selection based on security level
  • Image result for rdp require the connection to be encrypted'
  • The last part would be to customize the RDP session to enable authentication and encryption

I think these steps mentioned should address the problem, but it seems we continue to see the same problem.

Oh well, on the journey to enlightenment, we need to be forever vigilant.

Todd

 

 
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/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-14540
PUBLISHED: 2019-09-15
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariConfig.
CVE-2019-16332
PUBLISHED: 2019-09-15
In the api-bearer-auth plugin before 20190907 for WordPress, the server parameter is not correctly filtered in the swagger-config.yaml.php file, and it is possible to inject JavaScript code, aka XSS.
CVE-2019-16333
PUBLISHED: 2019-09-15
GetSimple CMS v3.3.15 has Persistent Cross-Site Scripting (XSS) in admin/theme-edit.php.
CVE-2019-16334
PUBLISHED: 2019-09-15
In Bludit v3.9.2, there is a persistent XSS vulnerability in the Categories -> Add New Category -> Name field. NOTE: this may overlap CVE-2017-16636.
CVE-2019-16335
PUBLISHED: 2019-09-15
A Polymorphic Typing issue was discovered in FasterXML jackson-databind before 2.9.10. It is related to com.zaxxer.hikari.HikariDataSource. This is a different vulnerability than CVE-2019-14540.