Blaster (computer worm)
The worm was first noticed and started spreading on August 11, 2003. The rate that it spread increased until the number of infections peaked on August 13, 2003. Once a network (such as a company or university) was infected, it spread quicker within the network because firewalls typically did not prevent internal machines from using a certain port. Filtering by ISPs and widespread publicity about the worm curbed the spread of Blaster.
On March 12, 2004, Jeffrey Lee Parson, an 18-year-old from Hopkins, Minnesota, was arrested for creating the B variant of the Blaster worm; he admitted responsibility and was sentenced to an 18-month prison term in January 2005.
Creation and effects
According to court papers, the original Blaster was created after security researchers from the Chinese group Xfocus reverse engineered the original Microsoft patch that allowed for execution of the attack.
The worm spreads by exploiting a buffer overflow discovered by the Polish security research group Last Stage of Delirium in the DCOM RPC service on the affected operating systems, for which a patch had been released one month earlier in MS03-026 and later in MS03-039. This allowed the worm to spread without users opening attachments simply by spamming itself to large numbers of random IP addresses. Four versions have been detected in the wild. These are the most well-known exploits of the original flaw in RPC, but there were in fact another 12 different vulnerabilities that did not see as much media attention.
The worm was programmed to start a SYN flood against port 80 of windowsupdate.com if the system date is after August 15 and before December 31st and after the 15th day of other months, thereby creating a distributed denial of service attack (DDoS) against the site. The damage to Microsoft was minimal as the site targeted was windowsupdate.com, rather than windowsupdate.microsoft.com, to which the former was redirected. Microsoft temporarily shut down the targeted site to minimize potential effects from the worm.
The worm's executable, MSBlast.exe, contains two messages. The first reads:
I just want to say LOVE YOU SAN!!
This message gave the worm the alternative name of Lovesan. The second reads:
billy gates why do you make this possible ? Stop making money
and fix your software!!
The worm also creates the following registry entry so that it is launched every time Windows starts:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\ windows auto update=msblast.exe
- May 28, 2003: Microsoft releases a patch that would protect users from an exploit in WebDAV that Welchia used. (Welchia used the same exploit as MSBlast but had an additional method of propagation that was fixed in this patch. This method was only used after 200,000 RPC DCOM attacks - the form that MSBlast used.)
- July 5, 2003: Timestamp for the patch that Microsoft releases on the 16th.
- July 16, 2003: Microsoft releases a patch that would protect users from the yet unknown MSBlast. At the same time they also released a bulletin describing the exploit.
- Around July 16, 2003: White hat hackers create proof-of-concept code verifying that the unpatched systems are vulnerable. The code was not released.
- July 17, 2003: CERT/CC releases a warning and suggests blocking port 135.
- July 21, 2003: CERT/CC suggests also blocking ports 139 and 445.
- July 25, 2003: xFocus releases information on how to exploit the RPC bug that Microsoft released the July 16 patch to fix.
- August 1, 2003: The U.S. issues an alert to be on the lookout for malware exploiting the RPC bug.
- Sometime prior to August 11, 2003: Other viruses using the RPC exploit exist.
- August 11, 2003: Original version of the worm appears on the Internet.
- August 11, 2003: Symantec Antivirus releases a rapid release protection update.
- August 11, 2003, evening: antivirus and security firms issued alerts to run Windows Update.
- August 12, 2003: The number of infected systems is reported at 30,000.
- August 13, 2003: Two new worms appear and begin to spread. (Sophos, a variant of MSBlast and W32/RpcSpybot-A, a totally new worm that used the same exploit) 
- August 15, 2003: The number of infected systems is reported at 423,000.
- August 16, 2003: DDoS attack against windowsupdate.com starts. (Largely unsuccessful because that URL is merely a redirect to the real site, windowsupdate.microsoft.com.)
- August 18, 2003: Microsoft issues an alert regarding MSBlast and its variants.
- August 18, 2003: The related helpful worm, Welchia, appears on the internet.
- August 19, 2003: Symantec upgrades their risk assessment of Welchia to "high" (category 4).
- August 25, 2003: McAfee lowers their risk assessment to "Medium".
- August 27, 2003: A potential DDoS attack against HP is discovered in one variant of the worm.
- January 1, 2004: Welchia deletes itself.
- January 13, 2004: Microsoft releases a stand-alone tool to remove the MSBlast worm and its variants.
- February 15, 2004: A variant of the related worm Welchia is discovered on the internet.
- February 26, 2004: Symantec lowers their risk assessment to "Low" (category 2). (Actually this pertains to the related worm Welchia, not to MSBlast itself.)
- March 12, 2004: McAfee lowers their risk assessment to "Low".
- April 21, 2004: Another variant is discovered.
- January 28, 2005: The creator of the "B" variant of MSBlaster is sentenced to 18 months in prison.
Although the worm can only spread on systems running Windows 2000 or Windows XP, it can cause instability in the RPC service on systems running other versions of Windows NT, including Windows Server 2003 and Windows XP Professional x64 Edition. In particular, the worm does not spread in Windows Server 2003 because Windows Server 2003 was compiled with the /GS switch, which detected the buffer overflow and shut the RPCSS process down. When infection occurs, the buffer overflow causes the RPC service to crash, leading Windows to display the following message and then automatically reboot, usually after 60 seconds.
This system is shutting down. Please save all work in progress and log off. Any unsaved changes will be lost. This shutdown was initiated by NT AUTHORITY\SYSTEM
Time before shutdown: hours:minutes:seconds
Windows must now restart because the Remote Procedure Call (RPC) Service terminated unexpectedly.
This was the first indication many users had an infection; it often occurred a few minutes after every startup on compromised machines. A simple resolution to stop countdown is to run the "shutdown /a" command, causing some side effects such as an empty (without users) Welcome Screen. The Welchia worm had a similar effect. Months later, the Sasser worm surfaced, which caused a similar message to appear.
- "CERT Advisory CA-2003-20: W32/Blaster worm". CERT/CC. 2003-08-14. Archived from the original on 2014-10-17. Retrieved 2018-11-03.
- "MS03-026: Buffer Overrun in RPC May Allow Code Execution". Microsoft Support. Microsoft Corporation. Retrieved 2018-11-03.
- McCarthy, Jack (2005-01-28). "Blaster worm author gets jail time". InfoWorld. Retrieved 2018-11-03.
An 18-month prison sentence is probably the best that Jeffrey Parson could have realistically hoped for. The U.S. authorities have demonstrated their determination to deal with virus writers and other cybercriminals," said Graham Cluley, senior technology consultant for security software company Sophos.
- Thomson, Iain (2003-09-01). "FBI arrests 'stupid' Blaster.B suspect". vnunet.com. Archived from the original on 2008-11-01. Retrieved 2018-11-03.
- "MSBlast W32.Blaster.Worm / LovSan :: removal instructions". able2know.org. 2003-08-12. Retrieved 2018-11-03.
- "W32.Blaster.Worm". Symantec. 2003-12-09. Retrieved 2018-11-03.
- "The Lifecycle of a Vulnerability" (PDF). internet Security Systems, Inc. 2005. Archived from the original (PDF) on 2016-12-24. Retrieved 2018-11-03.
- "Worm:Win32/Msblast.A". Microsoft Corporation. Retrieved 2018-11-03.
- Bransfield, Gene (2003-12-18). "The Welchia Worm" (PDF). pp. 14, 17. Retrieved 2018-11-03.
- "Buffer Overrun in Windows Kernel Message Handling could Lead to Elevated Privileges (811493)". Retrieved 2018-11-03.
- "Flaw In Microsoft Windows RPC Implementation". 2003-07-16. Archived from the original on 2016-03-04.
- "Buffer Overflow in Microsoft RPC". 2003-08-08. Archived from the original on 2014-07-15. Retrieved 2018-11-03.
- "The Analysis of LSD's Buffer Overrun in Windows RPC Interface". 2003-07-25. Archived from the original on 2018-02-17. Retrieved 2018-11-03.
- Roberts, Paul F. (2003-08-12). "Blaster worm spreading, experts warn of attack". Retrieved 2018-11-03.
- Roberts, Paul F. (2003-08-13). "New Blaster worm variant on the loose". InfoWorld. Retrieved 2018-11-03.
- Roberts, Paul F. (2003-08-18). "Blaster worm attack a bust". InfoWorld. Retrieved 2018-11-03.
- "Virus alert about the Blaster worm and its variants". Microsoft Support. Microsoft Corporation. Retrieved 2018-11-03.
- "W32.Welchia.Worm". Symantec. 2017-08-11. Retrieved 2018-11-03.
- Naraine, Ryan (2003-08-19). "'Friendly' Welchia Worm Wreaking Havoc". InternetNews.com. Retrieved 2018-11-03.
- "Virus Profile: W32/Lovsan.worm.a". McAfee. 2003-08-11. Retrieved 2018-11-03.
- "A tool is available to remove Blaster worm and Nachi worm infections from computers that are running Windows 2000 or Windows XP". Microsoft Support. Microsoft Corporation. Archived from the original on 2014-08-06. Retrieved 2018-11-03.
- "W32.Welchia.C.Worm". Symantec. 2007-02-13. Retrieved 2018-11-03.
- "Minnesota Man Sentenced to 18 Months in Prison for Creating and Unleashing a Variant of the MS Blaster Computer Worm". 2005-01-28. Archived from the original on 2014-07-14. Retrieved 2018-11-03.
- Howard, Michael (2004-05-23). "Why Blaster did not infect Windows Server 2003". Microsoft Developer. Microsoft Corporation. Retrieved 2018-11-03.
- "Worm_MSBlast.A". TrendMicro.com. Retrieved 2018-11-03.
- "Blaster Worm-Virus or Its Variants Cause the Computer to Shutdown with an NT AUTHORITY\SYSTEM Error Message Regarding Remote Procedure Call (RPC) Service". HP Consumer Support. HP. Archived from the original on 2014-11-10. Retrieved 2018-11-03.
- "Blaster Worm". Techopedia. Retrieved 2018-11-03.