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.

Comments
Microsoft Patches Wormable RCE Vulns in Remote Desktop Services
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

 

 


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.