Top Qs
Timeline
Chat
Perspective
Sasser (computer worm)
A 2005 Windows [[computer worm]] From Wikipedia, the free encyclopedia
Remove ads
Sasser is a computer worm that affects computers running vulnerable versions of the Windows XP and Windows 2000 operating systems. Sasser spreads by exploiting the system through a vulnerable port and can spread without user intervention. It is stopped by a properly configured firewall or by downloading system updates from Windows Update. The specific hole Sasser exploits was documented and patched by Microsoft prior to the release of the worm.
 | This article includes a list of general references, but it lacks sufficient corresponding inline citations. (June 2025) |
The most characteristic experience of the worm is the shutdown timer that appears due to the worm crashing LSASS. Sasser impacted various organizations including Agence France-Presse (AFP) having all its satellite communications blocked for hours and the U.S. flight company Delta Air Lines having to cancel several trans-Atlantic flights.
Remove ads
History
The Sasser computer worm was created on April 29, 2004.[1] The LSASS vulnerability was patched by Microsoft in the April 2004 installment of its monthly security packages,[2] prior to the release of the worm.
Behavior
Summarize
Perspective
The specific hole Sasser exploits is documented by Microsoft in its MS04-011 bulletin (CVE-2003-0533).[3] Sasser spreads by exploiting the system through a vulnerable port. Thus, it is particularly virulent in that it can spread without user intervention, but it is also easily stopped by a properly configured firewall or by downloading system updates from Windows Update.
The worm was named Sasser because it spreads by exploiting a buffer overflow in the component known as LSASS (Local Security Authority Subsystem Service) on the affected operating systems (vulnerable versions of the Microsoft operating systems Windows XP and Windows 2000). This buffer overflow relies on an undocumented API call to Microsoft Active Directory, which both allows for unchecked remote queries and crashes LSASS.exe if given a long string.[4]
Once on a machine, the worm scans different ranges of IP addresses and connects to victims' computers primarily through TCP port 445. If a vulnerable installation of Microsoft's Windows XP and Windows 2000 is found, the worm utilizes its own FTP server hosted on previously infected machines to download itself onto the newly compromised host. Microsoft's analysis of the worm indicates that it may also spread through port 139. Several variants called Sasser.B, Sasser.C, and Sasser.D appeared within days (with the original named Sasser.A).
Side effects
An indication of the worm's infection of a given PC is the existence of the files C:\win.log, C:\win2.log or C:\WINDOWS\avserve2.exe on the PC's hard disk, the ftp.exe running randomly and 100% CPU usage, as well as seemingly random crashes with LSA Shell (Export Version) caused by faulty code used in the worm.
The most characteristic symptom of the worm is the shutdown timer that appears due to the worm crashing LSASS.exe.
Mitigation
The specific hole Sasser exploits is documented by Microsoft in its MS04-011 bulletin (CVE-2003-0533),[3] for which a patch had been released seventeen days earlier.[2] It is easily stopped by a properly configured firewall or by downloading system updates from Windows Update.
Remove ads
Impact
The impact of Sasser included the news agency Agence France-Presse (AFP) having all its satellite communications blocked for hours and the U.S. flight company Delta Air Lines having to cancel several trans-Atlantic flights because its computer systems had been swamped by the worm. The Nordic insurance company If and their Finnish owners Sampo Bank came to a complete halt and had to close their 130 offices in Finland. The British Coastguard had its electronic mapping service disabled for a few hours, and Goldman Sachs, Deutsche Post, and the European Commission also had issues with the worm. The X-ray department at Lund University Hospital had all their four layer X-ray machines disabled for several hours and had to redirect emergency X-ray patients to a nearby hospital.
Some technology specialists speculated that the worm writer reverse-engineered the patch to discover the vulnerability, which would open millions of computers whose operating system had not been upgraded with the security update.[5]
Author
On 7 May 2004, an 19-year-old German named Sven Jaschan from Rotenburg, Lower Saxony, then student at a technical college, was arrested for writing the worm. German authorities were led to Jaschan partly because of information obtained in response to a bounty offer by Microsoft of US$250,000.
One of Jaschan's friends had informed Microsoft that his friend had created the worm. He further revealed that not only Sasser, but also Netsky.AC, a variant of the Netsky worm, was his creation. Another variation of Sasser, Sasser.E, was found to be circulating shortly after the arrest. It was the only variation that attempted to remove other worms from the infected computer, much in the way Netsky does.
Jaschan was tried as a minor because the German courts determined that he created the worm before he was 18. The worm itself had been released on his 18th birthday (29 April 2004). Sven Jaschan was found guilty of computer sabotage and illegally altering data. On Friday, 8 July 2005, he received a 21-month suspended sentence.
Remove ads
Remediation
Workarounds
- The shutdown sequence can be aborted by pressing start and using the Run command to enter
shutdown /a. This aborts the system shutdown so the user may continue what they were doing.[a] - A second option to stop the worm from shutting down a computer is to change the time and/or date on its clock to the past; the shutdown time will move as far into the future as the clock was set back.
Removal
The Sasser worm can be stopped by pressing start and using the Run command to enter shutdown /a. This will abort the shutdown caused by the termination of lsass.exe, allowing the user more time to remove the worm.
The worm may be removed by running regedit.exe and navigating to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. There, the user must remove the avserve2.exe string. Next, the user must terminate avserve2.exe in task manager. Next, the user must navigate to C:\ and delete win2.log. Finally, the user must navigate to C:\Windows and delete avserve2.exe and reboot. After that reboot, the user's PC will no longer be infected with Sasser.
Remove ads
See also
Notes
References
External links
Wikiwand - on
Seamless Wikipedia browsing. On steroids.
Remove ads