RCP

[Mandi]

It looks like this problem is everywhere!! does microsoft
realize what is going on???
any fixers yet???

[Mcploppy ©]

Mandi bashed at the keyboard and said :

> It looks like this problem is everywhere!! does microsoft
> realize what is going on???
> any fixers yet???

W32.Blaster.Worm
http://www.symantec.com/avcenter/venc/data/w32.blaster.worm.html

Microsoft Windows DCOM RPC Interface Buffer Overrun Vulnerability
http://www.sarc.com/avcenter/security/Content/8205.html

Install the Microsoft patch:
Buffer Overrun In RPC Interface Could Allow Code Execution (823980)
http://www.microsoft.com/technet/security/bulletin/MS03-026.asp

--
Mcploppy ©

{ Remove both MyShoes to email me}
{ Homepage: http://tinyurl.com/bbel }
{ Local Radio: http://tinyurl.com/j1vi }
{ Download Messenger 6 http://tinyurl.com/h7co }

[Kent W. England [MVP]]

Microsoft announced a critical update on 16 July and I have been harping
on the issue since 17 July. Where have you been?

This is a symptom of the RPC/DCOM exploit as described in Microsoft
security bulletin MS03-026. Go to
http://www.microsoft.com/security/security_bulletins/ms03-026.asp to
read about this vulnerability.

You need to download the Windows critical update patch 823980 and enable
or install a personal firewall to block TCP and UDP ports 135, 139, and
445. The built-in XP firewall will block these ports by default.

Once you download what you need, disconnect from the network, install
your patch, install your firewall and clean the worm from your system.
For msblast.exe removal instructions, read
http://www.bigblackglasses.com/Article.aspx?Article=342.

Once you are sure your system is clean, you can reconnect to the
Internet. It is very important to address this quickly and to disconnect
as soon as possible. Your system is very vulnerable to further exploits
while the worm is present and you do not want your system involved in
the massive denial-of-service attacks that are coming in the next few
days from the masses of compromised systems.

Download, disconnect, patch, firewall, and clean. Then inspect. When
sure, reconnect.

--
Kent W. England, Microsoft MVP for Windows



"Mandi" > wrote in
message ...

> It looks like this problem is everywhere!! does microsoft
> realize what is going on???
> any fixers yet???