Re: nessus scan
From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 06/27/04
- Previous message: Joe Richards [MVP]: "Re: Admin members and passwords"
- In reply to: BOFH: "nessus scan"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 27 Jun 2004 14:42:35 -0400
NULL BIND which is your question #2 is part of the LDAP V3 standard. You have to
be able to bind in a non-credential to find out what types of security you can
use with an LDAP server.
-- Joe Richards Microsoft MVP Windows Server Directory Services www.joeware.net BOFH wrote: > As a part of our new policy to port scan everything several times a year > using nessus, we have come across a couple of things when scanning our > fully patched windows 2003 enterprise servers: > > 1. It was possible to log into the remote host using a NULL session. The > concept of a NULL session is to provide a null username and a null password, > which grants the user the 'guest' access. > > To prevent null sessions, see MS KB Article Q143474 (NT 4.0) and Q246261 > (Windows 2000). > Note that this won't completely disable null sessions, but will prevent them > from connecting to IPC$ > Please see http://msgs.securepoint.com/cgi-bin/get/nessus-0204/50/1.html > > I have set the restrictanonymous registry key to 1 and 2 (with reboots > between the changes) and every scan I run I always get the above message. > Is there a way to disable 'guest' access? Is there some KB Article I missed > that discusses NULL sessions and windows 2003? > > 2. How do I disable NULL BIND on my LDAP servers? I am not running > exchange. > > Thank you for your time, > > BOFH1234 > >
- Previous message: Joe Richards [MVP]: "Re: Admin members and passwords"
- In reply to: BOFH: "nessus scan"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
