Microsoft July Black Tuesday Overview

Published: 2009-07-14
Last Updated: 2009-07-14 17:34:08 UTC
by Swa Frantzen (Version: 1)
4 comment(s)

Overview of the July 2009 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS09-028 Multiple vulnerabilities exist in DirectX and allow for arbitrary code execution with the rights of the logged on user.
Replaces MS08-033 and MS09-011.

KB 971633

Active exploitation of CVE-2009-1537

Addresses SA971778

MS09-029 Multiple input validation vulnerabilities allow for arbitrary code execution with the rights of the logged on user.
Replaces MS06-002.
.eot (Embedded OpenType)

KB 961371 No known exploits Severity:Critical
Critical Important
MS09-030 An input validation error allows arbitrary code to be executed with the rights of the logged on user.

KB 969516 No known exploits Severity:Important
Critical Important
MS09-031 When using Radius OTP authentication, a user can bypass authentication leading to privilege escalation and access to resources.
ISA server 2006

KB 970953 No known exploits Severity:Important
N/A Critical
MS09-032 Cumulative killbit update, adds killbits for the recently discussed video ActiveX control.
Note there are recently discovered killbits one should set that are not included in this update.
Replaces MS08-032.
ActiveX killbits

KB 973346 Workaround for active exploitation included
MS09-033 A privilege escalation problem exists in the handling of privileged instructions on the guest OS.
Virtual PC, Virtual server

KB 969856 No known exploits Severity:Important
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 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

(**): Assuming a worst case scenario

(***): If you use virtual server to create a shared environment and have users accessing virtual machines while not allowing them to manage the system, make that critical.

Swa Frantzen -- Section 66

4 comment(s)


Has anyone else noticed that the patches don't seem to require reboots, but yet all of my system are requiring MS09-029 and the Security Update Deployment details for all OSes claim "Yes, you must restart your system after you apply this security update." What gives? Which hand is confused - the one that wrote the security bulletin, or the one that developed the deployment package? I'm playing it safe and deploying a post-update job to force a reboot, but it'd be nice to see some clarification from Microsoft on this.
yes, saw the same myself, no reboot prompted for by the updates.
See for -ehm- clearification: "Some notes on restart requirements: One of the three updates for Windows will require a restart, the others may if the DLL being updated is in use.[...] Note however that the Virtual PC/Virtual Server update will not prompt you so you should factor a manual restart in to your deployment plans as soon as possible."
MS09-029 has been updated:
"V1.1 (July 15, 2009): Clarified a FAQ about the workaround from Microsoft Security Advisory 972890, added a FAQ about Microsoft Security Advisory 973472, and added a FAQ about the kill bits contained in this bulletin"
There are updates for/in MS09-033, MS09-032 and MS09-030 too.

Diary Archives