Sasser (computer worm): Difference between revisions
No edit summary |
Added removal section, describing removal process for Sasser worm. |
||
| (37 intermediate revisions by 31 users not shown) | |||
| Line 1: | Line 1: | ||
{{Short description|None}} |
|||
{{Unreferenced|date=May 2015}} |
|||
{{Infobox computer virus |
{{Infobox computer virus |
||
| fullname = Sasser Worm |
| fullname = Sasser Worm |
||
| Line 11: | Line 10: | ||
* Net-Worm:W32/Sasser ([[F-Secure]]) |
* Net-Worm:W32/Sasser ([[F-Secure]]) |
||
* Net-Worm:W32/Sasser.[Letter] (F-secure) |
* Net-Worm:W32/Sasser.[Letter] (F-secure) |
||
* W32.Sasser.Worm ([[Symantec]]) |
* W32.Sasser.Worm ([[NortonLifeLock|Symantec]]) |
||
* W32.Sasser.[Letter] (Symantec) |
* W32.Sasser.[Letter] (Symantec) |
||
* W32.Sasser.[Letter].Worm (Symantec) |
* W32.Sasser.[Letter].Worm (Symantec) |
||
| Line 36: | Line 35: | ||
}} |
}} |
||
'''Sasser''' is a [[computer worm]] that affects computers running vulnerable versions of the [[Microsoft]] [[operating systems]] [[Windows XP]] and [[Windows 2000]]. Sasser spreads by exploiting the system through a vulnerable [[Port (computer networking)|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 (networking)|firewall]] or by downloading system updates from [[Windows Update]]. The specific hole Sasser exploits is documented by Microsoft in its [http:// |
'''Sasser''' is a [[computer worm]] that affects computers running vulnerable versions of the [[Microsoft]] [[operating systems]] [[Windows XP]] and [[Windows 2000]]. Sasser spreads by exploiting the system through a vulnerable [[Port (computer networking)|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 (networking)|firewall]] or by downloading system updates from [[Windows Update]]. The specific hole Sasser exploits is documented by Microsoft in its [http://technet.microsoft.com/en-us/security/bulletin/ms04-011 MS04-011] bulletin, for which a patch had been released seventeen days earlier.<ref>{{Cite web |date=Nov 11, 2004 |title=Win32/Sasser |url=https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Win32/Sasser |url-status=live |archive-url=https://web.archive.org/web/20221031111650/https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Win32/Sasser |archive-date=31 October 2022 |access-date=6 Feb 2023 |website=Microsoft Security Intelligence}}</ref> The most characteristic experience of the worm is the shutdown timer that appears due to the worm crashing [[Local Security Authority Subsystem Service|LSASS]]. |
||
==History and effects== |
==History and effects== |
||
Sasser was |
Sasser was created on April 30, 2004.<ref>{{Cite web |last=Macrae |first=Duncan |date=2014-04-11 |title=Everything you need to know about the Sasser worm |url=https://techmonitor.ai/technology/cybersecurity/everything-you-need-to-know-about-the-sasser-worm-4213147 |access-date=2023-02-06 |website=Tech Monitor |language=en-US}}</ref> This 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. According to a report by eEye Digital Security published on April 13, 2004, this buffer overflow relies on an apparently deprecated API call to Microsoft Active Directory, which both allows for unchecked remote queries and crashes LSASS.exe if given a long string.<ref>{{Cite web |date=2006-01-09 |title=Network Security, Vulnerability Assessment, Intrusion Prevention |url=http://www.eeye.com/html/Research/Advisories/AD20040413C.html |archive-url=https://web.archive.org/web/20060109033004/http://www.eeye.com/html/Research/Advisories/AD20040413C.html |url-status=dead |archive-date=2006-01-09 |access-date=2023-02-06 }}</ref> Once on a machine, the worm scans different ranges of [[IP address]]es and connects to victims' computers primarily through [[Transmission Control Protocol|TCP]] port 445. If a vulnerable installation of XP or 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). The LSASS vulnerability was patched by Microsoft in the April 2004 installment of its monthly security packages, prior to the release of the worm. Some technology specialists have 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.<ref>{{Citation |title=Net-Worm.Win32.Sasser On a Physical PC Network |url=https://www.youtube.com/watch?v=BhtyEdhepIc |language=en |access-date=2023-02-06}}</ref> |
||
The effects of Sasser |
The effects of Sasser included the [[news agency]] [[Agence France-Presse]] (AFP) having all its satellite communications blocked for hours and the [[United States|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 countries|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 [[United Kingdom|British]] [[Her Majesty's Coastguard|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 machine]]s disabled for several hours and had to redirect emergency X-ray patients to a nearby hospital. |
||
==Author== |
==Author== |
||
On 7 May 2004, 18-year-old [[Germany|German]] |
On 7 May 2004, an 18-year-old [[Germany|German]] named [[Sven Jaschan]] from [[Rotenburg an der Wümme|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. |
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. |
||
| Line 54: | Line 53: | ||
==Workarounds== |
==Workarounds== |
||
The shutdown sequence can be aborted by pressing start and using the '''Run''' command to enter <code>shutdown |
The shutdown sequence can be aborted by pressing start and using the '''Run''' command to enter <code>shutdown /a</code>. This aborts the system shutdown so the user may continue what they were doing. The shutdown.exe file is not available by default within Windows 2000, but can be installed from the Windows 2000 resource kit. It is available in Windows XP. |
||
A second option to stop the worm from shutting down a computer is to change the time and/or date on its clock to earlier; the shutdown time will move as far into the future as the clock was set back. |
A second option to stop the worm from shutting down a computer is to change the time and/or date on its clock to earlier; the shutdown time will move as far into the future as the clock was set back. |
||
== Removal == |
|||
The Sasser worm can be removed by pressing start and using the '''Run''' command to enter <code>shutdown /a</code>. 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 <code>regedit.exe</code> and navigating to <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run</code>. There, the user must remove the <code>avserve2.exe</code> string. Next, the user must terminate <code>avserve2.exe</code> in task manager. Next, the user must navigate to <code>C:\</code> and delete <code>win2.log</code>. Finally, the user must navigate to <code>C:\Windows</code> and delete <code>avserve2.exe</code> and reboot. After a reboot, the user's PC will no longer be infected with Sasser. |
|||
==See also== |
==See also== |
||
* [[Blaster (computer worm)]] |
* [[Blaster (computer worm)]] |
||
* [[Welchia|Nachia (computer worm)]] |
|||
* [[BlueKeep (security vulnerability)]] |
* [[BlueKeep (security vulnerability)]] |
||
* [[Timeline of notable computer viruses and worms]] |
* [[Timeline of notable computer viruses and worms]] |
||
==References== |
|||
{{Reflist}} |
|||
==External links== |
==External links== |
||
* [https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2004/ms04-011 Microsoft Security Bulletin: MS04-011] |
* [https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2004/ms04-011 Microsoft Security Bulletin: MS04-011] |
||
* {{CVE|2003-0533|candidate=yes}} |
|||
* [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0533 CVE: CAN-2003-0533] |
|||
* [http://www.securityfocus.com/bid/10108 Bugtraq ID 10108] |
* [http://www.securityfocus.com/bid/10108 Bugtraq ID 10108] |
||
* [http://www.microsoft.com/security/incident/sasser.mspx Read here how you can protect your PC (Microsoft Security page)] - Includes links to the info pages of major anti-virus companies. |
* [http://www.microsoft.com/security/incident/sasser.mspx Read here how you can protect your PC (Microsoft Security page)] - Includes links to the info pages of major anti-virus companies. |
||
| Line 72: | Line 78: | ||
* [http://news.bbc.co.uk/2/hi/technology/4649361.stm German admits creating Sasser (BBC News)] |
* [http://news.bbc.co.uk/2/hi/technology/4649361.stm German admits creating Sasser (BBC News)] |
||
* [http://news.bbc.co.uk/2/hi/technology/4659329.stm Sasser creator avoids jail term (BBC News)] |
* [http://news.bbc.co.uk/2/hi/technology/4659329.stm Sasser creator avoids jail term (BBC News)] |
||
<!-- Interwiki links (links to the same article in other languages) follow. Sorted alphabetically by language code --> |
<!-- Interwiki links (links to the same article in other languages) follow. Sorted alphabetically by language code --> |
||
{{Hacking in the 2000s}} |
{{Hacking in the 2000s}} |
||
| Line 81: | Line 85: | ||
[[Category:Exploit-based worms]] |
[[Category:Exploit-based worms]] |
||
[[Category:Hacking in the 2000s]] |
[[Category:Hacking in the 2000s]] |
||
[[Category:Windows malware]] |
|||
Latest revision as of 07:10, 20 May 2024
| Sasser | |
|---|---|
| Technical name |
|
| Type | Worm |
| Authors | Sven Jaschan |
| Technical details | |
| Platform | Windows 2000, Windows XP |
Sasser is a computer worm that affects computers running vulnerable versions of the Microsoft operating systems Windows XP and Windows 2000. 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 specific hole Sasser exploits is documented by Microsoft in its MS04-011 bulletin, for which a patch had been released seventeen days earlier.[1] The most characteristic experience of the worm is the shutdown timer that appears due to the worm crashing LSASS.
History and effects
[edit]Sasser was created on April 30, 2004.[2] This 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. According to a report by eEye Digital Security published on April 13, 2004, this buffer overflow relies on an apparently deprecated API call to Microsoft Active Directory, which both allows for unchecked remote queries and crashes LSASS.exe if given a long string.[3] 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 XP or 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). The LSASS vulnerability was patched by Microsoft in the April 2004 installment of its monthly security packages, prior to the release of the worm. Some technology specialists have 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.[4]
The effects 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.
Author
[edit]On 7 May 2004, an 18-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.
Side effects
[edit]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.
Workarounds
[edit]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. The shutdown.exe file is not available by default within Windows 2000, but can be installed from the Windows 2000 resource kit. It is available in Windows XP.
A second option to stop the worm from shutting down a computer is to change the time and/or date on its clock to earlier; the shutdown time will move as far into the future as the clock was set back.
Removal
[edit]The Sasser worm can be removed 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 a reboot, the user's PC will no longer be infected with Sasser.
See also
[edit]- Blaster (computer worm)
- Nachia (computer worm)
- BlueKeep (security vulnerability)
- Timeline of notable computer viruses and worms
References
[edit]- ^ "Win32/Sasser". Microsoft Security Intelligence. Nov 11, 2004. Archived from the original on 31 October 2022. Retrieved 6 Feb 2023.
- ^ Macrae, Duncan (2014-04-11). "Everything you need to know about the Sasser worm". Tech Monitor. Retrieved 2023-02-06.
- ^ "Network Security, Vulnerability Assessment, Intrusion Prevention". 2006-01-09. Archived from the original on 2006-01-09. Retrieved 2023-02-06.
- ^ Net-Worm.Win32.Sasser On a Physical PC Network, retrieved 2023-02-06
External links
[edit]- Microsoft Security Bulletin: MS04-011
- CAN-2003-0533
- Bugtraq ID 10108
- Read here how you can protect your PC (Microsoft Security page) - Includes links to the info pages of major anti-virus companies.
- New Windows Worm on the Loose (Slashdot article)
- Report on the effects of the worm from the BBC
- German admits creating Sasser (BBC News)
- Sasser creator avoids jail term (BBC News)