Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Security IT

10 Years After SQL Slammer 58

Posted by Soulskill
from the lesson-learned dept.
Trailrunner7 writes "Ten years ago today, on Jan. 25, 2003, a new worm took the Internet by storm, infecting thousands of servers running Microsoft's SQL Server software every minute. The worm, which became known as SQL Slammer, eventually became the fastest-spreading worm ever and helped change the way Microsoft approached security and reshaped the way many researchers handled advisories and exploit code. This is the inside story of SQL Slammer, told by David Litchfield, the researcher who found the bug and wrote the exploit code that was later taken by Slammer's authors and used as part of the worm."
This discussion has been archived. No new comments can be posted.

10 Years After SQL Slammer

Comments Filter:
  • Google Cache Version (Score:5, Informative)

    by Anonymous Coward on Friday January 25, 2013 @04:38PM (#42695061)
  • by nweaver (113078) on Friday January 25, 2013 @04:47PM (#42695139) Homepage

    We (David Moore, Vern Paxson, Stefan Savage, Colleen Shannon, Stuart Staniford, and myself) did the analysis of how it spread, including showing how it infected all the vulnerable systems in 10 minutes, and detailing flaws in the random number generator.

    Our article eventually appeared in IEEE Security & Privacy [ieee.org].

  • by eap (91469) on Friday January 25, 2013 @05:00PM (#42695271) Journal

    So this guy "wrote the exploit code that was later taken by Slammer's authors and used as part of the worm", and he's not dead or serving an eleventy hojillion year federal prison sentence?

    Times change indeed...

    The article mentions he was paid by a company in Germany to penetrate their heavily-fortified SQL Server installations. This is when he developed the exploit code. Presumably it's not illegal for a company to pay you to security test its systems.

    He also took the steps of communicating the exploit to Microsoft before releasing the code. He even asked their permission before divulging the code, and didn't do so until MS had released a fully corrective patch.

    You're right, however, he'd be in jail if it happened today.

At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.