Microsoft May 2012 Black Tuesday Update - Overview

Published: 2012-05-08
Last Updated: 2012-05-08 18:06:14 UTC
by Adam Swanger (Version: 1)
4 comment(s)

Overview of the May 2012 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS12-029 Microsoft Word RTF Import
(Replaces MS10-079, MS11-089, MS11-094)
Microsoft Word 2003 and 2007
KB 2680352 No publicly known exploits Severity:Critical
Exploitability: 1
MS12-030 Microsoft Office Remote Code Execution Vulnerabilities
(Replaces MS11-072, MS11-089, MS11-094, MS11-096)
Microsoft Excel 2003/2007/2010
KB 2663830 Yes (CVE-2012-0143) Severity:Critical
Exploitability: 3,3,1,1,2,1
MS12-031 Visio Viewer 2010 Remote Code Execution Vulnerability
(Replaces MS12-015)
Microsoft Visio Viewer 2010
KB 2597981 No publicly known exploits Severity:Important
Exploitability: 1
MS12-032 TCP/IP Elevation of Privilege and Firewall Bypass Vulnerability
(Replaces MS11-083)
TCP/IP, Windows Firewall
KB 2597981 No publicly known exploits Severity:Important
Exploitability: 1
important important
MS12-033 Vulnerability in Windows Client/Server Run-time Subsystem Could Allow Elevation of Privilege
Plug and Play (PnP) Configuration Manager Vulnerability
KB 2690533 Elevation of Privilege Severity:Important
Exploitability: Likely
Important Important
MS12-034 Combined Security Update for Microsoft Office, Windows, .NET Framework, and Silverlight
(Replaces MS11-029, MS12-018)
Microsoft Windows, Microsoft .NET Framework, Microsoft Silverlight, Microsoft Office
KB 2681578 Yes Severity:Critical
Exploitability: 1,1,1,1,2,1,1,1,1,1
MS12-035 .Net Framework Remote Code Execution
(Replaces MS11-044, MS11-078, MS12-016)
.NET Framework
KB 2693777 No publicly known exploits Severity:Critical
Exploitability: 1
We will update issues on this page for about a week or so as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
(*): ISC rating
  • We use 4 levels:
    • PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.
    • Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.
    • Important: Things where more testing and other measures can help.
    • Less Urgent: Typically we expect the impact if left unpatched to be not that big a deal in the short term. Do not forget them however.
  • The difference between the client and server rating is based on how you use the affected machine. We take into account the typical client and server deployment in the usage of the machine and the common measures people typically have in place already. Measures we presume are simple best practices for servers such as not using outlook, MSIE, word etc. to do traditional office or leisure work.
  • The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threat for affected systems. The rating does not account for the number of affected systems there are. It is for an affected system in a t ypical worst-case role.
  • Only the organization itself is in a position to do a full risk analysis involving the presence (or lack of) affected systems, the actually implemented measures, the impact on their operation and the value of the assets involved.
  • All patches released by a vendor are important enough to have a close look if you use the affected systems. There is little incentive for vendors to publicize patches that do not have some form of risk to them.

(**): The exploitability rating we show is the worst of them all due to the too large number of ratings Microsoft assigns to some of the patches.


Adam Swanger, Web Developer (GWEB, GWAPT)
Internet Storm Center -

4 comment(s)


Seeing failures of KB2686509 - which is actually documented in but in my own personal case there is no faultykeyboard.log file

Seeing people in the answers forum hitting it as well:
KB2686509 repeatedly fails with Error code 0x8007F0F4
Microsoft is Still Serving up the April 2012 version 4.7 of the W7X64 Flavor of the Malicious Software Removal Tool;
Not the May 2012 V.4.8

x86 version is being served up but no joy on x64.
They Have been releasing Something to run on the machines at update time but who knows exactly what that is?

The KB article link for MS12-032 needs to be edited to point to KB2688338 ( )
They finally got it released on the server;
about ten minutes ago I got it d/l'd;

Diary Archives