Re: How is dangerous connect to server over internet with remote d

Hi,

I did a search and I found one DoS vulnerability from the past:

Microsoft Security Advisory (904797)
Vulnerability in Remote Desktop Protocol (RDP) Could Lead to Denial of
Service
http://www.microsoft.com/technet/security/advisory/904797.mspx

--
Mike
Microsoft MVP - Windows Security

"Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
news:ehewxSNrGHA.2464@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I can't recall any critical vulnerabilities in the past in Terminal
Services. I consider it a very good solution for remote access and
administration even without IP filtering. As mentioned the only concern is
how strong and protected your passwords are.

--
Mike
Microsoft MVP - Windows Security

"Massimo" <Massimo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC61C683-818C-4FEF-A912-73767BB69894@xxxxxxxxxxxxxxxx
Thank'you very much for you answer. I want know if there are in the
past..
bug or vulenability in the terminal service (remote desktop). If i use
encryption and if i connect to server with the same ip ( i configure
firewall
to accept only my remote fixed ip for 3389 port) can i consider this
solution
a good solution for manage the server?

"Miha Pihler [MVP]" wrote:

Hi,

There are few things you can do to make these connections (more) secure:
- On the server set the encryption to high
- On Windows Server 2003 with SP1 installed on it you can use
certificates
to prevent MITM (Man In The Middle) attacks.

Now the only thing that I usually worry about when considering RDP are
key
loggers that might be installed on a computer from which you are trying
to
connect to your server (e.g. if you are trying to connect to your server
from cyber café). Still this is not only the problem with RDP connection
but
with any remote connection using static username and password.

So if you decide for this option pay attention to username and password
(use
strong username and password and change passwords frequently). Don't use
domain administrator account for connection - use ordinary user account.
Whenever possible this user account should not even be local
administrator
on the server. Once you are connected to the server you can raise your
permissions using another RDP to the server or options such as "run as"
etc.

Another thing to consider is to limit IP address from which you can
connect
to your server over RDP (e.g. limit it to your home IP address only).

--
Mike
Microsoft MVP - Windows Security

"Massimo" <Massimo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0E85C1B9-1460-4EF8-8EFC-7FF4FD983C45@xxxxxxxxxxxxxxxx
I have installed windows server 2003 enterprise edition. I have to
manage
my
server from remote site. A solution with remote desktop only is very
dangerous? Terminal service of windows server 2003 with encryption is
not
secure?

Thank's







.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #171
    ... Better Management for Network Security ... GoodTech Telnet Server Remote Denial Of Service Vulnerabilit... ... ASPApp PortalAPP Remote User Database Access Vulnerability ...
    (Focus-Microsoft)
  • RE: Windows Remote Desktop
    ... Terminal Server then apply that to the appropriate part of your Domain ... On the topic of securing RDP i was wondering if anyone can help.... ... Now everything works fine but Im still security concious and would like to ... >We provide Ethical Hacking, Advanced Ethical Hacking, Intrusion ...
    (Security-Basics)
  • Re: Windows Remote Desktop
    ... On the topic of securing RDP i was wondering if anyone can help.... ... Now everything works fine but Im still security concious and would like to ... If you get a hold of the certificate the server presents to the ... >We provide Ethical Hacking, Advanced Ethical Hacking, Intrusion ...
    (Security-Basics)
  • Re: Terminal Services Setup/Flaw
    ... I was able to login to the Terminal Server with this user and then .rdp into another server on the network using the same credentials. ... I found the Remote Desktop Users group but that's not being used. ... "moncho" wrote: ...
    (microsoft.public.windows.terminal_services)
  • Re: DomainLocalServer$ is not a valid user
    ... it can be a BIG security hole. ... Local System or Network Service account on a machine makes a remote request ... things have access to your SQL Server. ...
    (microsoft.public.sqlserver.security)