Study: Slammer was fastest spreading worm yet

A just-completed study into the Slammer worm that hit the Internet a week ago has concluded what many people already suspected: Slammer represented a significant milestone in the evolution of worms and was by far the fastest spreading worm yet seen.

Free IT resource Hear how top CIOs turn change into a competitive advantage. Sponsored by HP Free IT resource Attend the SOA Executive Forum: Breaking SOA Bottlenecks SOAExecForum.com/may2007 Sponsored by InfoWorld

The study was conducted by a group of experts representing the Cooperative Association for Internet Data Analysis (CAIDA), International Computer Science Institute, Silicon Defense, University of California at Berkeley 's Electrical Engineering and Computer Sciences department and the University of California at San Diego Computer Science and Engineering department.

Its results provide a look into the first moments of the spread of Slammer and provides some impressive statistics.

During the first three minutes of the worm's spread, the number of infected machines doubled roughly every 8.5 seconds, the study found. This is more than 250 times faster than Code Red, which hit in mid-2001 and had a doubling time of 37 minutes, according to the report. The worm hit its full scanning rate of around 55 million scans per second at around three minutes after the attack began at roughly 05:30 GMT on Saturday.

The result of this fast spread was that within ten minutes of the start of the attack the majority of the estimated 75,000 machines that were hit had been infected, said the report.

Slammer's spread was considerably faster for several reasons, said the report. First, it was small. At just 376 bytes in size, the worm and required headers fit inside a 404-byte UDP (Universal Datagram Protocol) packet. Code Red was 4Kb in size while the Nimda worm was around 37Kb.

The worm also worked differently to Code Red. Slammer generated random IP addresses and dispatched itself to those addresses without scanning to find out whether the target machine was running either of the two pieces of software that were vulnerable to attack: Microsoft's SQL Server 2000 database and MSDE 2000 (Microsoft SQL Server 2000 Data Engine). Because of its random nature, the worm would hit all vulnerable machines given enough time.

However, the speed with which it propagated appears to have contributed to its downfall. Spread of the worm eventually began to slow because bandwidth from infected machines to the Internet could not support the exponential growth in IP packets being generated, the report said.

Its signature, attacking a specific port on vulnerable systems, was also easy to detect and network-level blocking of the ports in question was effective in slowing the worm.

In the case of Code Red, the worm probed machines to find vulnerable servers and only attacked IP addresses of machines judged vulnerable. This led to a much slower rate of spread.

The report also identified at least one implication of the attack.

It said smaller user populations could potentially be more vulnerable to attack. In the past, worms often only targeted software for which there was a large installed base of users. But given the speed with which Slammer-like worms can spread, less popular software now also presents a viable breeding ground for worms, the report said.

Full details of the study can be found online at http://www.caida.org/analysis/security/sapphire/.