Solved

Windows Remote Desktop Protocol Private Key Disclosure

Posted on 2009-05-13
5
1,059 Views
Last Modified: 2012-05-06
Hi Experts:

Our security scan shows us that we have a vunerbility called "Windows Remote Desktop Protocol Private Key Disclosure". I have searched all over the internet but can't seem to find a solution.
Could someone what I need to do to fix this?
We are running Windows server 2003 R2 with SP2.
Thanks
0
Comment
Question by:changjia
  • 2
  • 2
5 Comments
 
LVL 12

Expert Comment

by:nsx106052
ID: 24378095
This article is pretty good on the issue you are seeing:
http://www.vulnerabilityscanning.com/Microsoft-Windows-Remote-Desktop-Protocol-Server-P-Test_18405.htm

Another thing to consider may be to create local firewall policies to only allow RDP traffic from the local subnet.  Also check to make sure the computer is up to date with all the latest MS security patches.
0
 

Author Comment

by:changjia
ID: 24378264
Hi Nsx106052,

From reading the article, I have learn that the solution is to Force the use of SSL as a transport layer for this service.

Do you know how to do that?

Thanks
0
 
LVL 12

Expert Comment

by:nsx106052
ID: 24378379
You will need to configure it in Group policy:

computer configuration/administrative templates/windows components/terminal services/encryption and security



0
 

Author Comment

by:changjia
ID: 24378688
It has always been set to high and require secure connection, how come the scan still shows the vunerbility?
Thanks
0
 
LVL 27

Accepted Solution

by:
Tolomir earned 500 total points
ID: 24603401
Well the problem still persists but you can circumvent it:

---
http://social.msdn.microsoft.com/forums/en-US/winserver2008appcompatabilityandcertification/thread/de9ad6db-f814-4f44-bd64-ddcf9173ab74/

This issue was "fixed" by adding SSL support to TS in W2K3 SP1 and CredSSP to Vista/W2K8.

In W2K3 this was:

BUG: 806509 - APPROVED DCR: ETA: 8/6 WS2003SP1: RDP is vulnerable to man-in-the-middle attack

It was a well-known TS security issue. The private key used to sign a proprietary certificate (which contains the generated TS public key) is hardcoded in the code (see MS-RDPBCGR section 5.3.3 for more details).

Take a look at (this discuss SSL in W2K3 SP1):

http://technet2.microsoft.com/WindowsServer/en/library/a92d8eb9-f53d-4e86-ac9b-29fd6146977b1033.mspx?mfr=true

---

So with SSL enabled this is no longer an issue. When you disable SSL it is an issue, so it is not repaired.

Tolomir
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Every computer eventually fails. When that happens, your valuable data is only as safe as your current backup.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message. In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now