OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Williams, Kevin (KWilliamssark.com)
Date: Wed Mar 13 2002 - 11:31:38 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Really? Wow. I might be able to accept that from ICS, but for a firewall to
    OPEN a port is inexcusable. I think the world would like to know why a
    firewall is opening a common port.

    -----Original Message-----
    From: Alex Elger [mailto:alex.elgermicronage.com]
    Sent: Wednesday, March 13, 2002 9:30 AM
    To: Williams, Kevin
    Subject: RE: Windows XP open port 389

    They all to that.
    Even windows 2000 running ics.

    Alex Elger
    Micronage Ltd
    alex.elgermicronage.com

    -----Original Message-----
    From: Williams, Kevin [mailto:KWilliamssark.com]
    Sent: 12 March 2002 6:11 PM
    To: 'focus-mssecurityfocus.com'
    Subject: Windows XP open port 389

    I ran a scan of my laptop and discovered port 389 (LDAP) was listening. I
    tried FPort to nail down the .EXE responsible, but it told me "Must be
    Admin" and quit (I was using an admin account at the time). I began shutting
    down services until I found the one listening - it was the ICS/ICF
    (firewall) service.

    Does anyone have any info on why ICF was listening for LDAP traffic? I
    didn't have any services configured, only ICMP allowed.