Microsoft June Black Tuesday Overview
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 appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
- 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
Adobe June Black Tuesday upgrades
In the past it was by accident, but from now on it'll be by policy: Adobe will add to the workload by releasing their patches on a quarterly schedule to concide with the Microsoft monthly scheme.
June yielded just one bulletin:
Affects Acrobat (Reader) on Windows and Mac to Adobe Reader 9.1.2 and Acrobat 9.1.2. Also available are Acrobat 8.1.6 and Acrobat 7.1.3.
This fixes following CVE names:
CVE-2009-0198, CVE-2009-0509, CVE-2009-0510, CVE-2009-0511, CVE-2009-0512, CVE-2009-0888, CVE-2009-0889, CVE-2009-1855, CVE-2009-1856, CVE-2009-1857, CVE-2009-1858, CVE-2009-1859, and CVE-2009-1861.
Note that the bulletin states "Additionally, this update resolves Adobe internally discovered issues".
Among the list are a number of JBIG2 filter vulnerabilities.
JBIG2 filter vulnerabilities have been exploited in the past, so you really want this upgrade.
UPDATE:
Roseman wrote in to point out the bulletin contains: "Security updates for Adobe Reader on the UNIX platform will be available on June 16, 2009". which effectively gives the attackers time to reverse engineer the vulnerabilities from the patches for Windows and Mac and build exploits for the unix versions without those users having any chance to patch.
--
Swa Frantzen -- Section 66
Safari 4.0 released - contains security fixes
Apple released yesterday an update to Safari 4.0 (which had been in beta for quite some time)
The release also contains a large number of fixes for security vulnerabilities:
CFNetwork: CVE-2009-1704, CVE-2009-1716
ImageIO: CVE-2009-0040
International components for Unicode: CVE-2009-0153
libxml: CVE-2008-3281, CVE-2008-3529, CVE-2008-4409, CVE-2008-4225, CVE-2008-4226
Safari: CVE-2009-1682, CVE-2009-1706, CVE-2009-1707, CVE-2009-1708
Safari windows installer (no CVE name)
Webkit: CVE-2006-2783, CVE-2008-1588, CVE-2008-2320, CVE-2008-3632, CVE-2008-4231, CVE-2009-1681, CVE-2009-1684, CVE-2009-1685, CVE-2009-1686, CVE-2009-1687, CVE-2009-1688, CVE-2009-1689, CVE-2009-1690, CVE-2009-1691, CVE-2009-1693, CVE-2009-1694, CVE-2009-1695, CVE-2009-1696, CVE-2009-1697, CVE-2009-1698, CVE-2009-1699, CVE-2009-1700, CVE-2009-1701, CVE-2009-1702, CVE-2009-1703, CVE-2009-1709, CVE-2009-1710, CVE-2009-1711, CVE-2009-1712, CVE-2009-1713, CVE-2009-1714, CVE-2009-1715, CVE-2009-1718
Needles to say, this update comes as highly recommended for anybody using safari.
Note some CVE names are quite old ... e.g. CVE-2006-2783 was first discussed more than 3 years ago in Mozilla (June 1st, 2006) and was fixed by Apple for iPhone and iPod almost a year ago (July 11th, 2008).
--
Swa Frantzen -- Section 66
Comments