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

 

 


Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Breaches Are Inevitable, So Embrace the Chaos
Ariel Zeitlin, Chief Technology Officer & Co-Founder, Guardicore,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-2916
PUBLISHED: 2019-11-15
qtnx 0.9 stores non-custom SSH keys in a world-readable configuration file. If a user has a world-readable or world-executable home directory, another local system user could obtain the private key used to connect to remote NX sessions.
CVE-2019-12757
PUBLISHED: 2019-11-15
Symantec Endpoint Protection (SEP), prior to 14.2 RU2 & 12.1 RU6 MP10 and Symantec Endpoint Protection Small Business Edition (SEP SBE) prior to 12.1 RU6 MP10d (12.1.7510.7002), may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt t...
CVE-2019-12758
PUBLISHED: 2019-11-15
Symantec Endpoint Protection, prior to 14.2 RU2, may be susceptible to an unsigned code execution vulnerability, which may allow an individual to execute code without a resident proper digital signature.
CVE-2019-12759
PUBLISHED: 2019-11-15
Symantec Endpoint Protection Manager (SEPM) and Symantec Mail Security for MS Exchange (SMSMSE), prior to versions 14.2 RU2 and 7.5.x respectively, may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software applicat...
CVE-2019-18372
PUBLISHED: 2019-11-15
Symantec Endpoint Protection, prior to 14.2 RU2, may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.