Threat Level: green Handler on Duty: Didier Stevens

SANS ISC: InfoSec Handlers Diary Blog - November 2013 Microsoft Patch Tuesday InfoSec Handlers Diary Blog

Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!

November 2013 Microsoft Patch Tuesday

Published: 2013-11-12
Last Updated: 2013-11-14 17:03:33 UTC
by Johannes Ullrich (Version: 1)
3 comment(s)

Overview of the November 2013 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS13-088 Cumulative Security Update for Internet Explorer
(ReplacesMS13-080 )
Internet Explorer
KB 2888505 No. Severity:Critical
Exploitability: 1,2,3
Critical Important
MS13-089 Remote Code Execution Vulnerability in Windows Graphics Device Interface
(ReplacesMS08-071 )
KB 2876331 No. Severity:Critical
Exploitability: 1
Critical Important
MS13-090 Remote Code Execution Vulnerability in InformationCardSigninHelp ActiveX Class
(ReplacesMS11-090 )
ActiveX (icardie.dll)
KB 2900986 Yes. Severity:Critical
Exploitability: 1
PATCH NOW! Important
MS13-091 Remote Code Execution Vulnerability in Microsoft Office
(ReplacesMS09-073 )
Microsoft Office (Word)
KB 2885093 No. Severity:Important
Exploitability: 1,3
Critical Important
MS13-092 Elevation of Privileges Vulnerability in HyperV
HyperV Guests (DoS for Host)
KB 2893986 No. Severity:Important
Exploitability: 1
Important Important
MS13-093 Information Disclosure Vulnerability in Ancillary Function Driver
(ReplacesMS12-009 )
Ancillary Function Driver
KB 2875783 No. Severity:Important
Exploitability: 3
Important Important
MS13-094 Information Disclosure Vulnerability in Outlook
(ReplacesMS13-068 )
KB 2894514 No. Severity:Important
Exploitability: 3
Important Less Important
MS13-095 Denial of Service Vulnerability in Digital Signatures
(ReplacesAdvisory 2661254 )
Digital Signatures
KB 2868626 No. Severity:Important
Exploitability: 3
N/A 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.

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

3 comment(s)
Diary Archives