RE: Command Line RPC vulnerability scanner?

From: Schmehl, Paul L (pauls_at_utdallas.edu)
Date: 07/31/03

  • Next message: Joe Matusiewicz: "Re: Scans for 17300/tcp starting again" 
    Date: Thu, 31 Jul 2003 10:30:31 -0500
To: <incidents@securityfocus.com>

    I have both eEye's tool and ISS's tool. I decided to run the ISS
    commandline scanner on our entire class B last night. That way I could
    come in this morning and have a complete report of patch compliance. Or
    so I thought. When I got in to my office this morning, the ISS tool had
    been running for 15 hours and had reported on a total of 99 hosts.

    I don't know what's wrong with it, but something obviously is.

    Paul Schmehl (pauls@utdallas.edu)
    Adjunct Information Security Officer
    The University of Texas at Dallas
    AVIEN Founding Member
    http://www.utdallas.edu/~pauls/

    > -----Original Message-----
    > From: Michael Wright [mailto:mcwright@dbls.com]
    > Sent: Wednesday, July 30, 2003 1:25 PM
    > To: JAMIE CRAWFORD; incidents@securityfocus.com
    > Subject: Re: Command Line RPC vulnerability scanner?
    >
    >
    > Yes. ISS provides one for windows:

    ---------------------------------------------------------------------------
    ----------------------------------------------------------------------------

  • Next message: Joe Matusiewicz: "Re: Scans for 17300/tcp starting again"

    Relevant Pages

    • RE: Command Line RPC vulnerability scanner?
      ... timeout of waiting for a 135 connection that is taking the tool so long. ... You just have to balance out the overhead of invoking the executable per IP ... I decided to run the ISS ... come in this morning and have a complete report of patch compliance. ...
      (Incidents)
    • Re: CRS report on INA and ISS
      ... Has anyone seen the report of the ISS "roadmap" meeting ...
      (sci.space.policy)