Every month the BugBlog picks its Bug of the Month, representing the most significant bug found in the past month. Sometimes, the bug will be the one which could potentially cause the most damage; sometimes it will be the bug which affects the most users. And sometimes, it will be the bug that just happens to be the most interesting. This bug will be selected either from the free Bug of the Day, or from the subscription-only BugBlog Plus.
The BugBlog Bug of the Month actually comes in two parts, both affecting portions of Microsoft Windows Media Player. They appeared on February 14, with the first portion appearing in the free Bug of the Day, and the second one in the BugBlog Plus.
The plug-in version of Microsoft Windows Media Player, which is designed to work within a web browser, appears to open up a serious security hole when it is used with non-Microsoft browsers from Mozilla and Netscape. If you are using the browser, and come upon a maliciously designed webpage that has content set up to play in Windows Media Player, and that content has a very long embed src tag, the attacker may be able to overwrite memory and run their code on your computer. Get the update from Microsoft. As a workaround, you can make sure that Windows Media Player is not the default plug-in for media files that you may run across. Microsoft credits iDefense for finding this bug. Note that the plug-in doesn’t cause problems for the Opera browser, nor from Microsoft Internet Explorer. (Does this mean if Microsoft can’t beat you in the market, they will destroy you from within? Nah, couldn’t be.)
Microsoft has a security update for most of the recent versions of Windows Media Player running on Windows 2000, XP and Server 2003. A remote attacker may be able to construct a malicious bitmap (.bmp) file that, if viewed on a website or email message, may allow the attacker to take complete control of your system. Again, Microsoft has the full listing of vulnerable versions, and links to patches. Microsoft credits Marc Maiffret of eEye for finding this bug.
Why these bugs? Well, they pass the Critical test — they can allow a remote attacker to take control of your computer. They are also widespread — given the market share of Windows XP, any problem with one of its components is going to cause some concern. Plus, truth be told, there wasn’t a lot of competition in February. But a win is still a win — so chalk up another Bug of the Month for Microsoft.Powered by Sidelines