full-disclosure - LDAP NULL Bind being picked up, making non PCI compliant

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <SNT115-W4740E73DC0ED9E602B7083EC8B0@phx.gbl>
Date: Wed, 1 Sep 2010 10:30:55 -0400
From: Jason Nada <j.crider@...e.com>
To: <full-disclosure@...ts.grok.org.uk>
Subject: LDAP NULL Bind being picked up,
	making non PCI compliant

We recently ran a scan against our exchange servers and got the error that our server was vulnerable to an LDAP NULL BIND overflow. This vulnerability is now making out network uncomplient to PCI and are having trouble with a way to fix the problem.

I know we can't deny or shut up down LDAP as it is needed by RootDSE, but we need to find a fix or way to stop the LDAP from being picked up as vulnerable. The server is runing Windows 2008, and from what I read is that Win 2008 will show the server as vulnerable but, doesn't really pose any kind of threat? Is this true? Any information will help! Thanks! 		 	   		  
Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/