February 2012 Microsoft Black Tuesday

Published: 2012-02-14
Last Updated: 2012-02-14 20:41:30 UTC
by Johannes Ullrich (Version: 1)
4 comment(s)

Overview of the February 2012 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS12-008 Code Execution Vulnerabilities in Windows Kernel-Mode Drivers
(Replaces MS11-087)
KB 2660465 disclosed vuln. Severity:Critical
Exploitability: Likely
Critical Critical
MS12-009 Elevation of privilege vulnerabilities in ancillary function driver
(Replaces MS11-046, MS11-080)
Ancillary Function Driver
KB 2645640 no. Severity:Important
Exploitability: Likely
Important Important
MS12-010 Cumulative Patch for Internet Explorer
(Replaces MS11-099)
Internet Explorer
KB 2647516 no. Severity:Critical
Exploitability: Likely
Critical Important
MS12-011 Sharepoint Elevation of Privileges Vulnerabilities
KB 2663841 no. Severity:Important
Exploitability: -
N/A Important
MS12-012 Remote code execution vulnerability in color control panel
Color Control Panel
KB 2643719 no. Severity:Important
Exploitability: Likely
Critical Important
MS12-013 Vulnerability in C Run-Time Library Could Allow Remote Code Execution
C Run Time Library
KB 2654428 no Severity:Critical
Exploitability: Likely
Critical Critical
MS12-014 Vulnerability in Indeo Codec Could Allow Remote Code Execution
Indeo Audio Codec
KB 2661637 no Severity:Important
Exploitability: Likely
Important N/A
MS12-015 Vulnerabilities in Microsoft Visio Viewer 2010 Could Allow Remote Code Execution
(Replaces MS11-089)
Microsoft Office Suites and Software
KB 2663510 no. Severity:Important
Exploitability: Likely
Important N/A
MS12-016 Vulnerabilities in .NET Framework and Microsoft Silverlight Could Allow Remote Code Execution
(Replaces MS11-069)
.NET Framework
KB 2651026 no. Severity:Critical
Exploitability: Likely
Critical Critical
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 typical 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.

Johannes B. Ullrich, Ph.D.
SANS Technology Institute

Keywords: mspatchday
4 comment(s)


Everything I am reading on the Microsoft page says patch MS12-012 is not applicable for any client operating systems. However, you have it identified as critical. Can you please clarify?

Be aware that KB2668562 Silverlight patch MS12-016 has been throwing off 80070643 errors. The update has been identified as having metadata issue by Microsoft and has been pulled out of the consumer channel. Hold off on approving this update in WSUS until it's been revised.
- Reason for Revision: V1.1 (February 14, 2012): Added an entry
to the update FAQ to announce a detection change for KB2668562
for Microsoft Silverlight 4 when installed on Windows clients
and servers to correct an installation issue. This is a detection
change only. There were no changes to the security update files.
Customers who have already successfully updated their systems
do not need to take any action.
- Originally posted: February 14, 2012
- Updated: February 14, 2012
The CVE for MS12-013 is wrong (that's actually the CVE for MS12-014). The proper CVE should be CVE-2012-0150

Diary Archives