Microsoft May 2013 Black Tuesday Overview

Published: 2013-05-14
Last Updated: 2013-05-15 00:12:31 UTC
by Swa Frantzen (Version: 1)
7 comment(s)

Overview of the May 2013 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS13-037 The usual monthly MSIE cumulative patch, adding fixes for 11 more vulnerabilities. All but one are use after free vulnerabilities. The odd one is about vbscript allowing read access to JSON data related to another domain.
Replaces MS13-028.

KB 2829530 No publicly known exploits Severity:Critical
Critical Important
MS13-038 The anticipated IE8 fix.
Note that IE9 is listed as affected as well, but it's not given a rating "because the known attack vectors for the vulnerability discussed in this bulletin are blocked in a default configuration."
Note that this is not the cumulatieve IE patch, nor is the fix part of the cumulative patch this month. The bulletin states there is no need to uninstall the MSFT Fix-it released earlier for this vulnerability.

KB 2847204 Publicly discussed and exploit code available. Security advisory 2847140 Severity:Critical
PATCH NOW Important
MS13-039 A vulnerability in the handling of HTTP headers in the HTTP stack allows a Denial of Service.

KB 2829254 No publicly known exploits. Severity:Important
Important Important
MS13-040 Incorrect validation of signed XML files allows for failing to detect changes in said files and an authentication bypass allowing unauthenticated access. The impact of these vulnerabilities high depends on what applications make use of these features.
Replaces MS10-041.

KB 2836440 Microsoft claims the vulnerability CVE-2013-1337 was publicly disclosed. Severity:Important
Important Important
MS13-041 A memory corruption vulnerability allows random code execution in the context of the current user.
Note the lync user level install of Lync 2010 Attendee is only available from the Microsoft Download Center - not via automatic updates.
Replaces MS12-066.

KB 2834695 No publicly known exploits. Severity:Important
Critical Important
MS13-042 A multitude of vulnerabilities in Publisher allow random code execution.
Replaces MS11-091.

KB 2830397 No publicly known exploits Severity:Important
Critical Important
MS13-043 Incorrect handling of shape data in word allows random code execution with the rights of the logged on user.
Note that when word is used to read incoming email messages, it can be affected merely via previewing incoming emailed RTF data!

KB 2830399 No publicly known exploits Severity:Important
Critical Important
MS13-044 A problem in handling XML files that references external files in Visio allows information leak and read access with the rights of the logged-on user.
Replace MS11-060 and MS13-023.

KB 2834692 No publicly known exploits. Severity:Important
Important Important
MS13-045 Windows Writer - part of the Windows Essentials package - is a client to manage blogs. The vulnerability allows overriding proxy settings and overwriting files accessible to the logged-on user.
Windows Essentials

KB 2813707 No publicly known exploits Severity:Important
Critical Important
MS13-046 Multiple vulnerabilities in Kernel Mode Drivers allow privilege escalation.
Replaces MS13-036 and MS13-031.
Kernel Mode Drivers

KB 2840221 No publicly known exploits Severity:Important
Imporant 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.

Swa Frantzen -- Section 66

7 comment(s)


There are a couple of typos in the desc. for MS13-042.
Fixed them typos in MS13-042 - I think.
Is anyone else having trouble loading some of the bulletins? I'm getting "We are sorry. The page you requested cannot be found." ( ) right now on 037, 038, 041, 044 and 045.
Yes I get the same error as well, was happening to some links of last months bulletins as well.
@Zinger & @Nate, I saw some of that yesterday and tracked it back to my use of the FF extension 'No-Script' blocking some of the MS domains, once I temporarily allowed them the page loaded OK. YMMV
How about the rating of a terminal server with IE8 (still) on it? IE will be heavily used here, as opposed to a not-in-use browser on a data-centric server.
Must it be treated as a win7/IE8 machine (patch now/high prio) or as a w2k8r2/IE8 box (patch with less prio)?

MS13-037 addressing Pwn2own vulnerabilities
14 May 2013

Diary Archives