


The ongoing prevalence of these worms through 2004 resulted in unpatched machines being infected within a matter of minutes. Several months later, the Sasser worm did something similar. In mid-2003, the Blaster worm attacked a large number of Windows machines, taking advantage of flaws in the RPC Windows service. It was disabled by default due to concerns with backward compatibility, and the configuration screens were buried away in network configuration screens that many users never looked at. When Windows XP was originally shipped in October 2001, it included a limited firewall called "Internet Connection Firewall".
