<?xml version="1.0" standalone="no"?>
                    <!DOCTYPE div SYSTEM "/www/backend/www-xml-443/dtd/caidaML.dtd">
                    <!-- do NOT ERASE the DOCTYPE declaration! --><div>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>Entry Date:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
2003-10-03


</font>
  </td>
</tr>


<tr bgcolor="#e9e9e9">
  <td>
<font face="helvetica,arial" size="2">
<b>URL:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<a href="http://www.caida.org/publications/papers/2003/sapphire/">http://www.caida.org/publications/papers/2003/sapphire/</a>
</font>
  </td>
</tr>


<tr bgcolor="#f4f4f4">
  <td>
<font face="helvetica,arial" size="2">
<b>Abstract:</b>
</font>
</td>
  <td>
<font face="helvetica,arial" size="2">
<p>The Sapphire Worm was the fastest computer worm in history.  As it
began spreading throughout the Internet, it doubled in size every 8.5
seconds.  It infected more than 90 percent of vulnerable hosts within
10 minutes.
</p><p>The worm (also called Slammer) began to infect
hosts slightly before 05:30 UTC on Saturday, January 25.  Sapphire
exploited a buffer overflow vulnerability in computers on the Internet
running Microsoft's SQL Server or MSDE 2000 (Microsoft SQL Server
Desktop Engine).  This weakness in an underlying indexing service was
discovered in July 2002; Microsoft released a patch for the
vulnerability before it was announced. The worm infected at least
75,000 hosts, perhaps considerably more, and caused network outages
and such unforeseen consequences as canceled airline flights,
interference with elections, and ATM failures.  Several disassembled
versions of the source code of the worm are available.
</p><p>Propagation speed was Sapphire's novel feature: in the first
minute, the infected population doubled in size every 8.5 (+/- 1)
<!-- this should be &plusmn;  don't know why it's not working here -->
seconds. The worm achieved its full scanning rate (over 55 million
scans per second) after approximately three minutes, after which the
rate of growth slowed down somewhat because significant portions of
the network did not have enough bandwidth to allow it to operate
unhindered. Most vulnerable machines were infected within 10-minutes
of the worm's release. Although worms with this rapid propagation had
been predicted on theoretical grounds, the spread of Sapphire provides
the first real incident demonstrating the capabilities of a high-speed
worm. By comparison, it was two orders magnitude faster than the Code
Red worm, which infected over 359,000 hosts on July 19th, 2001. In
comparison, the Code Red worm population had a leisurely doubling time
of about 37 minutes.
</p><p>While Sapphire did not contain a malicious payload, it caused
considerable harm simply by overloading networks and taking database
servers out of operation. Many individual sites lost connectivity as
their access bandwidth was saturated by local copies of the worm and
there were several reports of Internet backbone disruption (although
most backbone providers appear to have remained stable throughout the
epidemic). It is important to realize that if the worm had carried a
malicious payload, had attacked a more widespread vulnerability, or
had targeted a more popular service, the effects would likely have
been far more severe.
</p><p>This document is a preliminary analysis of the Sapphire worm,
principally focused on determining the speed and scope of its spread
and the mechanisms that were used to achieve this result.
</p>



</font>
  </td>
</tr>
</div>
