Securtiy of forwarding RDP

Jan 11, 2006 6 Replies
Securtiy of forwarding RDP open original image

In my PIX, I have a rule set up to forward Remote Desktop (port 3389) through to one of my servers:



static (inside,outside) tcp interface 3389 192.168.1.5 3389 netmask



255.255.255.255 0 0

Another rule was created to allow RDP to another server. Since 3389 was already used, we used 3390, which is forward through to 3389 on the other server:



static (inside,outside) tcp interface 3390 192.168.1.6 3389 netmask



255.255.255.255 0 0

My question is - is this safe? And would it be safe to do the same thing to allow RDP directly to my workstation - say forward 3391 to my ip address?



Thanks, Mike


Well, no it's not safe. Is it safe enough for you? I can't answer that.

It's succeptible to man in the middle, you've made no mention of enryption, anyone can poke away at the password, you've made no mention of strong authentication.

Were I to be tasked with hacking your network, this would be by far the easiest route, since simply getting your username and password (insert dozen different methods here) would yield me complete control of a workstation inside the LAN.

-Russ.

formatting link
the encryption level to high and you'll be fine.

Wayne McGlinn Brisbane, Oz

formatting link
Maybe RDP is a good idea in a VPN or via SSH.

Yours, VB.

In message , Wayne writes

But then never mentions them again!

Anyone know where control of encryption is in XP?

I am in complete agreement with Volker here. I only use RDP inside the network or over encrypted VPN. Opening an RDP port like that to the Internet is a major security hole.

  1. MS RDP is not a safe protocol. see
    formatting link
    and the other security vulnerabilities of this protocol.
  2. If you still want to use MSRDP I would recommend you rename the Administrator account to something else and rename the Guest account to Administrator and make sure it is disabled.
  3. try to restrict the IPs that can connect to it from remote. i.e. you know that the only persons that are going to connect to it are you and another admin, add a firewall rule to restrict the connections to your homes DSL IPs
  4. change the outside ports to something not in the 33xx range, ex. use
7621, 59923...
  1. if possible use an IPSEC gateway to encrypt the traffic between you & the PIX

Mike Bailey wrote:

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required