Dave420
09-14-2003, 09:04 PM
http://grc.com/dcom/
this is a great little program to turn off DCOM
What's the problem?
The problem is that this very powerful DCOM system, which allows pieces of your computer to be remotely activated and used from across a network -- even by any stranger across the Internet -- is always enabled in Windows systems by default. Microsoft's most recent DCOM patch, which fixes another (not the first) remotely exploitable vulnerability in this complex system, continues to defiantly leave the whole DCOM system exposed and enabled . . . and waiting for the next vulnerability to be discovered.
What's the solution?
Just turn it off. No Internet applications use or require DCOM. Some Windows applications support it, but those that do neither use nor require it. As with so many of Windows' easily avoided security vulnerabilities, Microsoft should never have chosen to enable DCOM by default, and they certainly should have had their most recent patch turn it off after the MSBlast worm event. But instead, all Windows systems are still running DCOM and waiting for the next disaster.
You and I have the responsibility to fix this correctly by just saying no to DCOM.
this is a great little program to turn off DCOM
What's the problem?
The problem is that this very powerful DCOM system, which allows pieces of your computer to be remotely activated and used from across a network -- even by any stranger across the Internet -- is always enabled in Windows systems by default. Microsoft's most recent DCOM patch, which fixes another (not the first) remotely exploitable vulnerability in this complex system, continues to defiantly leave the whole DCOM system exposed and enabled . . . and waiting for the next vulnerability to be discovered.
What's the solution?
Just turn it off. No Internet applications use or require DCOM. Some Windows applications support it, but those that do neither use nor require it. As with so many of Windows' easily avoided security vulnerabilities, Microsoft should never have chosen to enable DCOM by default, and they certainly should have had their most recent patch turn it off after the MSBlast worm event. But instead, all Windows systems are still running DCOM and waiting for the next disaster.
You and I have the responsibility to fix this correctly by just saying no to DCOM.