Leaked code still could bear malicious fruit
When news of the leak of a portion of Windows source code broke last month, many in the security community cautioned against overreacting, saying that the leak likely wouldn't lead to a slew of new vulnerability discoveries. But that attitude has changed in recent weeks because researchers said that crackers have uncovered several previously unknown vulnerabilities in the code and appear determined to keep the flaws quiet for their private use.
Many in the legitimate security world have shied away from downloading and examining the code, out of fear of legal problems with Microsoft and out of a desire to keep their research unspoiled by what could be corrupt or damaged code. However, malicious crackers have had no such reservations. Immediately following the code's posting on the Internet, members of the security underground began poring over the code, searching for undocumented features and flaws that might give them a new way to break into Windows machines.
By Dennis Fisher at eWeek.
[ Read more ]
- News: UK provider warns users about leaked Windows code (4 March 2004)
- News: Mainsoft put in spotlight over leaked source code (23 February 2004)
- News: A quick look at the Win2k source (19 February 2004)
- News: Code leak flaw may exist, admits Microsoft (19 February 2004)
- News: Exploit based on leaked Windows code released (17 February 2004)
- News: Windows code leak 'not a security threat' (13 February 2004)
- Review: HackNotes Windows Security Portable Reference (13 October 2003)