Amie
09-04-2003, 07:37 AM
Steve Gibson, who many of you know as the creator of the
free and excellent "ShieldsUp" security testing service,
wrote this week:
Hi Fred, I wanted to let you know, so that you
could tell your readers if you think it's worthy,
that I have just (early this morning) released my
latest freeware: The DCOMbobulator.
http://grc.com/dcom/
The DCOMbobulator does two things:
* It allows any Windows user to easily test and
verify that their Windows' DCOM system *has* been
correctly patched to eliminate the serious remote
exploit vulnerability which recently brought us
all of the MSBlast Internet worm excitement. We
have confirmed reports that Microsoft's patch
sometimes does not "take", leaving Windows still
vulnerable. The DCOMbobulator let's anyone check
any local Windows system.
* Secondly, and really most importantly, since
virtually NO ONE needs (or has ever needed) to
have DCOM running, the DCOMbobulator allows any
Windows user to safely and easily disable DCOM and
unbind it from port 135. I do a comprehensive job
of this on ALL versions of Windows, so that if the
Windows Task Scheduler and the "Distributed
Transaction Coordinator" (MSDTC) services -- which
both also use port 135 -- are also disabled,
Windows TCP port 135 will finally be closed. )
Like Steve's other offerings, the DCOMbobulator is tiny,
fast, free, and efficient: It downloads in a flash, and does
just what Steve says (above). Plus, it explains what it's
doing, and why; and offers an ultra-easy way to reverse the
changes, if you should ever need or want to. Nice!
I have just used this on my system and here was the result, so I know it works.
free and excellent "ShieldsUp" security testing service,
wrote this week:
Hi Fred, I wanted to let you know, so that you
could tell your readers if you think it's worthy,
that I have just (early this morning) released my
latest freeware: The DCOMbobulator.
http://grc.com/dcom/
The DCOMbobulator does two things:
* It allows any Windows user to easily test and
verify that their Windows' DCOM system *has* been
correctly patched to eliminate the serious remote
exploit vulnerability which recently brought us
all of the MSBlast Internet worm excitement. We
have confirmed reports that Microsoft's patch
sometimes does not "take", leaving Windows still
vulnerable. The DCOMbobulator let's anyone check
any local Windows system.
* Secondly, and really most importantly, since
virtually NO ONE needs (or has ever needed) to
have DCOM running, the DCOMbobulator allows any
Windows user to safely and easily disable DCOM and
unbind it from port 135. I do a comprehensive job
of this on ALL versions of Windows, so that if the
Windows Task Scheduler and the "Distributed
Transaction Coordinator" (MSDTC) services -- which
both also use port 135 -- are also disabled,
Windows TCP port 135 will finally be closed. )
Like Steve's other offerings, the DCOMbobulator is tiny,
fast, free, and efficient: It downloads in a flash, and does
just what Steve says (above). Plus, it explains what it's
doing, and why; and offers an ultra-easy way to reverse the
changes, if you should ever need or want to. Nice!
I have just used this on my system and here was the result, so I know it works.