Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Plugin 18405

Subject: Re: Plugin 18405
Date: Tue, 10 Jul 2007 17:24:47 +0200

On Jul 10, 2007, at 5:00 PM, Nelson, C.M. wrote:

Plugin 18405 very sensibly generates this report:

"Synopsis : It may be possible to get access to the remote host.
Description : The remote version of Remote Desktop Protocol Server
(Terminal Service) is vulnerable to a man in the middle attack. An
attacker may exploit this flaw to decrypt communications between  
client
and server and obtain sensitive information (passwords  ...)."

When distributing Nessus reports I have to explain that where terminal
services must be enabled then the scope of exposure of the service
should be minimised, probably using the Windows host-based  
firewall, and
that the accounts exposed should have very strong passwords. This is
because I think remote brute force or dictionary log-in attempts using
e.g. TSgrinder could be more of a concern that the possibility of a
sophisticated man in the middle attack. I'm not sure whether other  
would
agree, however, it would make my life a little easier if the scope and
password strength aspects could also be explained in the plug-in  
output.



This plugin tests that the terminal service is vulnerable to the MiM  
attack (by checking the rsa key is fixed) but does not test that the  
password is weak. So we can't add that to the plugin output because  
it is not linked with the test.


Nicolas
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>