SQL Slammer: a small worm with a very large traffic problem
PERIOD
2003
EDITION
Short field file
REVIEWED
2026-11-19
The short version
On January 25, 2003, Slammer spread through vulnerable SQL Server 2000 and MSDE 2000 systems. Microsoft describes it as memory-resident and propagating over UDP port 1434. A fix for the underlying vulnerability had been available before the outbreak.
Why it moved so quickly
The research team’s account describes a 376-byte worm carried in a single UDP packet. It scanned randomly for susceptible computers. Unlike a propagation method that waits for a connection handshake, it could keep sending attempts rapidly. The researchers describe bandwidth as a major constraint.
Infection and disruption are different things
Cisco reported heavy traffic, overloaded devices, and dropped traffic. Its advisory also warned that blocking the propagation channel did not remove infections already inside a network. An outage on a network therefore did not mean every affected computer was infected.
Don’t let the graph write the motive
The researchers explain that network saturation and failures changed the observed growth curve. A slowdown on a chart is not, by itself, evidence that an operator chose to ease off. Automated spreading, network conditions, and the observer’s vantage point all matter.
From the workbench
Before choosing a fix, name the problem: an infected host, excessive network traffic, or a service somebody cannot reach. Those can overlap, but they are not interchangeable. This is an investigative takeaway, not present-day remediation guidance for an unsupported system.
What this file leaves open
This account does not identify the author or assign intent to individual outages. It omits a definitive infection total, numerical growth-rate claims, and the Davis-Besse case until their additional context is reviewed.
