Microsoft June Black Tuesday Overview

Published: 2009-06-09. Last Updated: 2009-06-10 13:01:38 UTC
by Swa Frantzen (Version: 2)
3 comment(s)

Overview of the June 2009 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS09-018 A vulnerability in freeing memory on Windows 2000 server leads to remote code execution and another one leads to DoS on active directory on Windows 2000 and 2003 server as well as ADAM installation on XP and server 2003.
Replaces MS08-060 and MS08-035.
Active Directory

CVE-2009-1138
CVE-2009-1139
KB 971055 No known exploits Severity:Critical
Exploitability:1,3
N/A Critical
MS09-019 A cumulative patch for IE. The worst of them leads to random code execution. Affects IE5.01 up to and including IE8.
Replaces MS09-014.
Internet Explorer

CVE-2007-3091
CVE-2009-1140
CVE-2009-1141
CVE-2009-1529
CVE-2009-1530
CVE-2009-1531
CVE-2009-1532
KB 969897 CVE-2007-3091 is publicly known with claims going as far back as May 2004 (unverified). Severity:Critical
Exploitability:
3,3,3,1,3,2,2,3,3
Critical Important
MS09-020 Input validation errors in the WebDAV extentions for IIS allow privilege escalation.
Webdav IIS

CVE-2009-1122
(CVE-2009-1535)
CVE-2009-1676
KB 970483 CVE-2009-1535, better known as CVE-2009-1676, is publicly known and covered in SA 971492. Severity:Important
Exploitability:3,1
N/A Important
MS09-021 A number of vulnerabilities allow random code execution.
Updates for Office for Mac versions are bundled with the fixes for MS09-017 and MS09-027.
Replaces MS09-009, MS08-057 and MS08-074
Excel

CVE-2009-0549
CVE-2009-0557
CVE-2009-0558
CVE-2009-0559
CVE-2009-0560
CVE-2009-0561
CVE-2009-1134
KB 969462 No known exploits Severity:Critical
Exploitability:
2,1,2,1,3,1,1
Critical Important
MS09-022 Vulnerabilities in th eprint spooler allow random code execution, Information leaks and Privilege escalation.
Replaces MS07-021.
print spooler

CVE-2009-0228
CVE-2009-0229
CVE-2009-0230
KB 961501 UPDATE: exploit available in for pay program Severity:Critical
Exploitability:
1,3,1
Important Important
MS09-023 A vulnerability in generating file previews allows HTML scripting to run on affected clients.
Windows Search

CVE-2009-0239
KB 963093 No known exploits Severity:Moderate
Exploitability:3
Important Less Urgent
MS09-024 A buffer overflow vulnerability allows code execution on affected systems.
Replaces MS08-072.
Works convertors

CVE-2009-1533
KB 957632 No known exploits Severity:Critical
Exploitability:1
Critical Important
MS09-025 Multiple vulnerabilities allow privilege escalation.
Replaces MS09-006.
Windows kernel desktop

CVE-2009-1123
CVE-2009-1124
CVE-2009-1125
CVE-2009-1126
KB 968537 Microsoft claims CVE-2009-1123 and CVE-2009-1126 are publicly known. Severity:Important
Exploitability:
2,1,1,1
Important Important
MS09-026 A vulnerability in the RPC marshalling engine allows privilege escalation and random code execution.
Replaces MS07-058.
RPC

CVE-2009-0568
KB 970238 Microsoft claims CVE-2009-0568 is publicly known. Severity:Important
Exploitability:2
Important Important
MS09-027 Multiple vulnerabilities allow random code execution.
Updates for Office for Mac versions are bundled with the fixes for MS09-017 and MS09-027.
Replaces MS08-072.
Word

CVE-2009-0563
CVE-2009-0565
KB 969514 No known exploits Severity:Critical
Exploitability:2,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

--
Swa Frantzen -- Section 66

3 comment(s)

Comments

Shouldn't the description on several of these read "remote code execution", not "random code execution"?
"remote code execution" is also what happens legitimately with every RPC call, with every downloaded -and executed- javascript, ...

Still, you're right in the sense that random code execution is an ability of an attacker, and the vulnerability is actually "arbitrary code execution". I'll try to remember to use that term next time.
It may be worth noticing the somewhat strange Security Advisory 971888 too: http://www.microsoft.com/technet/security/advisory/971888.mspx

Diary Archives