- Oct 12, 1999
- 5,704
- 2
- 0
Info:
http://www.cert.org/advisories/CA-2003-19.html
http://www.cert.org/tech_tips/win-UNIX-system_compromise.html
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html
This worm hits your TCP port 135, and it is the cause of the reboot problems many have posted about in Windows NT, 2K, and XP. Firewalls like Zone Alarm, etc. appear to trap the port hits.
If you use Windows NT, 2K or XP, visit the Windows Update site. This worm does NOT attack Windows 98 or ME, but your firewall may report
hundreds of port probes per hour.
Symantec's site says, if you find MSBLAST.EXE on your system, you have been infected.
http://www.cert.org/advisories/CA-2003-19.html
http://www.cert.org/tech_tips/win-UNIX-system_compromise.html
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html
This worm hits your TCP port 135, and it is the cause of the reboot problems many have posted about in Windows NT, 2K, and XP. Firewalls like Zone Alarm, etc. appear to trap the port hits.
If you use Windows NT, 2K or XP, visit the Windows Update site. This worm does NOT attack Windows 98 or ME, but your firewall may report
hundreds of port probes per hour.
Symantec's site says, if you find MSBLAST.EXE on your system, you have been infected.