December 2015 Microsoft Patch Tuesday

Published: 2015-12-08
Last Updated: 2015-12-08 18:07:10 UTC
by Johannes Ullrich (Version: 1)
19 comment(s)

Special Note: MS15-127 looks particularly "nasty". A remote code execution vulnerability in Microsoft's DNS server. Microsoft rates the exploitability as "2", but doesn't provide much details as to the nature of the vulnerability other than the fact that it can be triggered by remote DNS requests, which is bad news in particular if you are using a Microsoft DNS server exposed to the public internet. In this case, I would certainly expedite this patch. This is the vulnerability to look out for this time around.

Overview of the December 2015 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS15-124 Cumulative Security Update for Internet Explorer (Replaces MS15-124 )
Internet Explorer
KB 3116180 no. Severity:Critical
Exploitability: 1-4
Critical Critical
MS15-125 Cumulative Security Update for Microsoft Edge (Replaces MS15-112 )
Microsoft Edge
CVE-2015-6140, CVE-2015-6142, CVE-2015-6148, CVE-2015-6151, CVE-2015-6153, CVE-2015-6154, CVE-2015-6155, CVE-2015-6158, CVE-2015-6159, CVE-2015-6161, CVE-2015-6168, CVE-2015-6169, CVE-2015-6170, CVE-2015-6176
KB 3116184 no. Severity:Critical
Exploitability: 1-4
Critical Critical
MS15-126 Cumulative Security Update for JScript and VBScript (Replaces MS15-066 )
JScript/VBScript (IE8,Vista and 2008 only)
KB 3116178 no. Severity:Critical
Exploitability: 2,1
Critical Critical
MS15-127 Remote Code Execution in Microsoft Windows DNS (Replaces MS12-017 )
Microsoft DNS Server
KB 3100465 no. Severity:Critical
Exploitability: 2
N/A Critical
MS15-128 Remote Code Execution Vulnerability in Microsoft Graphics Component (Replaces MS15-115 )
various components (.Net, Lync, Silverlight, Skype..)
KB 3104503 no. Severity:Critical
Exploitability: 1,1,1
Critical Critical
MS15-129 Remote Code Execution in Microsoft Silverlight (Replaces MS15-080 )
KB 3106614 no. Severity:Critical
Exploitability: 2,2,1
Critical Important
MS15-130 Remote Code Execution in Microsoft Uniscribe (Replaces MS14-036 )
KB 3108670 no. Severity:Critical
Exploitability: 3
Critical Important
MS15-131 Remote Code Execution Vulnerability in Microsoft Office (Replaces MS15-116 )
KB 3116111 no. Severity:Critical
Exploitability: 1,1,1,1,1,1
Critical Important
MS15-132 Remote Code Execution in Microsoft Windows (Replaces MS15-122 MS15-115 )
KB 3116162 no. Severity:Important
Exploitability: 2,2,2
Critical Important
MS15-133 Privilege Escalation Vulnerability in Windows PGM
Microsoft Message Queuing (MSMQ)
KB 3116130 no. Severity:Important
Exploitability: 2
Important Important
MS15-134 Remote Code Execution in Windows Media Center (Replaces MS15-100 )
Windows Media Center
KB 3108669 no. Severity:Important
Exploitability: 2,2
Critical Important
MS15-135 Privilege Elevation Vulnerability in Windows Kernel-Mode Drivers (Replaces MS15-122 MS15-115 )
Kernel-Mode Drivers (Library Loading)
KB 3119075 yes (CVE-2015-6175). Severity:Important
Exploitability: 1,1,1,4
Important 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 a\ re 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 tim\ e to test.
    • Important: Things where more testing and other measures can help.
    • Less Urt 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 threatatches.

Johannes B. Ullrich, Ph.D.

Keywords: mspatchday
19 comment(s)


Anyone besides me notice that out of the 15 patches for Edge, 11 are shared with IE? Sorta makes you wonder how much of a "rewritten from scratch" code base it really is, no? :)
Early testing in our Windows 7 x64 Office 2010 environment has resulted in:

All machines launching Outlook in 'Safe Mode'.

Views, default settings and font preferences all blown out.

After last Month's attempt to get MS to pull a patch; 20 points of contact and 10+ hours wasted.

I will not be contacting them.

Microsoft... You are broken!!!

I pay you $20k+ a year for what?
The chart only renders properly in IE and Chrome, it fails in Firefox 42.
After much time removing updates one by one, I have determined that the broken KB that is causing Outlook to launch in Safe Mode is:



PLEASE PULL KB3114409 from Windows Update and STOP BREAKING COMPUTERS.
I have KB3114409 installed on 2 systems so far and don't see any problems.

Win7Pro/64bit - Office 2010/32bit

I did experience a problem where one computer froze at 15% during the Windows Update reboot. I let it sit for 40 mins before I did a hard reset. All was well after the reset thankfully!!
It definitely broke the 3 machines I began testing on.

There are a million reasons for something to appear in our production environment and not on another machine.

The problem is that MS no longer supports their products despite us spending large sums of corporate money on their 'Software Assurance'.

They have chosen to cheap out on 'support' to the point where it is impossible to alert them to a problem.

This leaves 'trial by public' as the only means to get their attention.
Check that.... I just did another reboot to check on a different problem.... (I had lost my Lync2010 integration) and now I DO see Outlook says it is in safe mode.

I probably missed that small type in the Outlook header the first time...and safe mode is probably why my Lync integration isn't working.
And just like for you, removing KB3114409 and rebooting fixed both problems.... Thanks for your testing and your reporting here....
I am seeing 32-bit Outlook 2010 going into Safe Mode on 32-bit and 64-bit Windows 7, as well as Windows Server 2008 R2 (Citrix XenApp 6.5). Uninstalling KB3114409 fixes it in all cases.

If KB3114409 is meant to fix CVE-2015-6124 (listed by MS as publicly exploited), then this is particularly unfortunate.
The format of your patch summary this month is broken. Looking at your page in full screen mode on a wide display I can only see the first column. I can't see your recommendations of the patch priority. (Or Microsofts which you usually have in a column.)

Diary Archives