Microsoft November 2012 Black Tuesday Update - Overview

Published: 2012-11-13
Last Updated: 2012-11-13 18:43:04 UTC
by Jim Clausing (Version: 1)
4 comment(s)

NOTE: Several of these patches apply to Windows 8 and Windows RT that were just released last month.

Overview of the November 2012 Microsoft patches and their status.


# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS12-071 Cumulative Security Update for Internet Explorer
(Replaces MS12-063 )
Internet Explorer 9
KB 2761451 no known exploit. Severity:Critical
Exploitability: 1,1,1
Critical Important
MS12-072 Vulnerabilities in Windows Shell Could Allow Remote Code Execution
(Replaces )
Remote Code Execution
KB 2727528 no known exploit. Severity:Critical
Exploitability: 1,1
Critical Critical
MS12-073 Vulnerabilities in Microsoft Internet Information Services (IIS) Could Allow Information Disclosure
(Replaces MS11-004 )
KB 2733829 PoC code may exist. Severity:Moderate
Exploitability: ?,?
Less urgent Important
MS12-074 Vulnerabilities in .NET Framework Could Allow Remote Code Execution
(Replaces MS11-078 MS11-100 MS12-016 MS12-034 )
.NET Framework 1.0 SP3, .NET Framework 1.1 SP1, .NET Framework 2.0 SP2, .NET Framework 3.5, .NET Framework 3.5.1, .NET Framework 4, .NET Framework 4.5
KB 2745030 no known exploit Severity:Critical
Exploitability: 1,3,1,1,1
Critical Critical
MS12-075 Vulnerabilities in Windows Kernel-Mode Drivers Could Allow Remote Code Execution
(Replaces MS12-055 )
Windows Vista, Windows 7, Windows 8, Windows RT, Windows Server 2003, Windows Server 2008, Windows Server 2012
KB 2761226 no known exploit Severity:Critical
Exploitability: 1,1,2
Critical Critical
MS12-076 Vulnerabilities in Microsoft Excel Could Allow Remote Code Execution (Replaces MS12-030 MS12-051 )
Excel 2003, Excel 2007, Excel 2010, Excel 2008 on Mac
KB 2720184 no known exploit Severity:Important
Exploitability: 1,1,1,1
Critical Important
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.

Post suggestions or comments in the section below or send us any questions or comments in the contact form

Jim Clausing, GIAC GSE #26
jclausing --at-- isc [dot] sans (dot) edu

4 comment(s)


After applying the updates, in the Network Notification Area, I get "Additional log on info may be required". And these messages stack, so if you don't so anything, you'll have a bunch to close. Who at MS thought this was a good idea??????? Maybe it only affects when connected via RDP as I do (all day), but I would like to see some info from MS on how to turn it off!
That is normally when you've connected to a new ISP/wireless. Is this happening after you reboot your machine?
Remove this:
Comments on that Open DNS forum now agree that the "Additional log on..." messages no longer appear. No need to remove KB 2750841 or to modify Open DNS control panel settings. No one reported seeing Open DNS describe the resolution.

Diary Archives