One of the links in previous message was erroneous, because MSRC Blog hyperlink pointed to the wrong URL. Correction follows: Microsoft has confirmed that it is a different vulnerability than this issue reported earlier this week: http://www.microsoft.com/technet/security/advisory/929433.mspx - Juha-Matti