Security Basics mailing list archives
Blocking port 4444 for W32.Blaster.Worm
From: Steven_Paice () cityofperth wa gov au
Date: Tue, 12 Aug 2003 10:57:22 +0800
Hi all, I have just been reading up on the Blaster Worm, and Symantec suggest blocking TCP port 4444 at the firewall level; I was wondering if anyone has implemented this yet and if so, if they have any feedback on the results regarding performance, risks etc. Thanks in advance Steven Paice --------------------------------------------------------------------------- ----------------------------------------------------------------------------
Current thread:
- Blocking port 4444 for W32.Blaster.Worm Steven_Paice (Aug 12)
- RE: Blocking port 4444 for W32.Blaster.Worm Michael LaSalvia (Aug 12)
- RE: Blocking port 4444 for W32.Blaster.Worm Steven_Paice (Aug 13)
- <Possible follow-ups>
- RE: Blocking port 4444 for W32.Blaster.Worm CHRIS GRABENSTEIN (Aug 12)
- Re: Blocking port 4444 for W32.Blaster.Worm Brett Munhall (Aug 20)
- Re: Blocking port 4444 for W32.Blaster.Worm chort (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm David Gillett (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm Dave Killion (Aug 20)
- RE: Blocking port 4444 for W32.Blaster.Worm Michael LaSalvia (Aug 12)