|
Current Windows exploits affecting campus via Microsoft RPC Buffer Overflow4What do I do if I am infected? 4What precautionary steps MUST everyone take?
On July 16th Microsoft announced a massive security hole in all versions of Windows. Technical details of the security hole is that it is a buffer overflow vulnerability in Windows Remote Procedure Call (RPC) implementation. For detailed information see the Microsoft security bulletin MS03-026 and the CERT advisory. There are currently at least three exploits on campus taking advantage of this vulnerability to infect computers; Trojan.Stealther.B, W32.Blaster.Worm, and W32.Welchia.Worm. Symptoms that you may be infected:
Steps to take if you are infected AND to secure your computer: First and foremost, anyone responsible for maintaining a computer running Windows should IMMEDIATELY visit the Windows Update Site http://windowsupdate.microsoft.com/ and install ALL critical and relevant security updates REGARDLESS of whether you are infected or not. If you think you have been infected with one of the exploits listed above, follow these steps:
Symantec has removal tools to help with the cleanup; Stealther Removal Tool, Blaster Removal Tool, and Welchia Removal Tool. *NOTE* Blaster only infects Windows 2000 and XP systems, but attempted infections on other versions of Windows may cause them to crash or misbehave. As part of its infection the Stealther Trojan disables real time protection mode in Symantec/Norton Anti-Virus, this is indicated by an exclamation ( ! ) mark over the yellow shield in your system tray (next to the clock). To fix this you will need to reinstall Symantec Anti-Virus after patching, cleaning, etc. Be sure to uninstall this version of Symantec Antivirus before reinstalling.
*NOTE* If you are not the administrator of your machine, contact your local system administrator, help desk, or tech support to verify your computer has been updated and cleaned. NC State Information Technology Division Jeff Webster - Security Coordinator Send questions or comments to help@ncsu.edu Last updated September 4, 2003 by jsw |