Early Patch Tuesday Today: Microsoft September 2011 Patches
Looks like Microsoft made the bulletins live that were supposed to be released this coming Tuesday. The bulletins are dated September 13th 2011. While the links below work as I type this diary, they may not work later today. Some of the related links may not have any information yet (like CVE). All bulletins appear to be live right now, and we will add them to the list below as we get to it.
This information may of course change as the final bulletins will be released on Tuesday. Some readers report that the bulletins are no longer available.
| # | Affected | Contra Indications - KB | Known Exploits | Microsoft rating(**) | ISC rating(*) | |
|---|---|---|---|---|---|---|
| clients | servers | |||||
| MS11-070 | Vulnerability in WINS could allow elevation of privilege. Replaces MS11-035. | |||||
| WINS CVE-2011-1984 |
KB 2571621 | - none - | Severity:Important Exploitability:? |
Important | Important | |
| MS11-071 | Vulnerability in Windows could allow remote code execution (DLL Linking Vuln.). | |||||
| Windows CVE-2011-1991 |
KB 2570947 | yes | Severity:Important Exploitability:? |
Critical | Important | |
| MS11-072 | Arbitrary code execution vulnerability in Excel. Replaces MS11-045. | |||||
| Excel CVE-2011-1986 CVE-2011-1986 CVE-2011-1987 CVE-2011-1988 CVE-2011-1989 CVE-2011-1990 |
KB 2587505 | - none - | Severity:Important Exploitability:? |
Critical | Important | |
| MS11-073 | Code execution vulnerability in Microsoft Office. Replaces MS11-023, MS10-087 . | |||||
| Office CVE-2011-1980 CVE-2011-1982 |
KB 2587634 | - none - | Severity:Important Exploitability:? |
Critical | Important | |
| MS11-074 | Microsoft Sharepoint Elevation of Privilege Vulnerability. Replaces MS11-016. | |||||
| Sharepoint CVE-2011-0653 CVE-2011-1252 CVE-2011-1890 CVE-2011-1891 CVE-2011-1892 CVE-2011-1893 |
KB 2481858 | CVE-2011-1252 publicly disclosed. some of the others are not disclosed but likely simple to exploit XSS flaws. | Severity:Important Exploitability:? |
-N/A- | 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.
(**): 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
Apple Certificate Trust Policy Update
Apple released a patch to update their certificate trust policy affecting Mac OS X Server 10.6, Mac OS X 10.6, Lion Server, OS X Lion. Using fraudulent certificates operated by DigiNotar, an attacker with enough network privileges could intercept user credentials or sensitive information. Apple recommends applying security update 2011-005, additional information available here and downloaded here.
Update 1: Apple has indicated that iOS users cannot remove the root cert and Apple is aware of the issue.
[1] http://support.apple.com/kb/HT4920
[2] http://www.apple.com/support/downloads/
[3] http://support.apple.com/kb/HT4415
-----------
Guy Bruneau IPSS Inc. gbruneau at isc dot sans dot edu
Community SANS SEC 503 coming to Ottawa Sep 2011
Large power outage in Southern California
Update: it appears that the outage of several Microsoft services was not related to the power outage. http://windowsteamblog.com/windows_live/b/windowslive/
Per the San Diego Gas and Electric web site, power has been restored to the majority of customers.
----
The San Diego area (including parts of Mexico and Arizona) are experiencing a large power outage due to a problem in a high voltage transmission line [1]. It may take until Friday for power to be restored. As a result, expect various internet outages to follow as UPSs run down.
Currently, it appears that MSN.com is at least partially down, and Hotmail.com (aka mail.live.com) is coming up with a home page but after logging in the connection fails. It is not clear if these outages are related to the power outage, but both sites do host some assets in the San Diego area.
Right now, there are no reports of wide spread routing failures.
If you do live in the area, and are still able to read this: Turn off air conditioners and it is best to stay off the roads as traffic signals are failing. Go to bed, get some sleep, and hope that things will be better in the morning as you get up ;-).
[1] http://www.sdge.com/
------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter
IPv6 and DNS Sinkhole
In January 2010, I posted a diary on how to configure zone files to setup a DNS sinkhole using IPv4 addresses. This updated diary shows how to add IPv6 support to your zone file to sinkhole both IPv4 and IPv6.
Single Hostname (/var/named/sinkhole/client.nowhere)
Wildcard Domain (/var/named/sinkhole/domain.nowhere)
Note: If you are not currently using IPv6 in your network, change the example fec0:0:0:bebb::5 to ::1 (localhost) to prevent 6to4, Toredo, etc from leaving the network.
To verify your zone files are correctly configured, you can use nslookup to query a hostname or a domain loaded in your sinkhole.
With Windows 7 (note that it shows both IPv4 and IPv6):
C:>nslookup zz87lhfda88.com
Server: seeker.someserver.com
Address: 192.168.25.5
Name: zz87lhfda88.com
Addresses:fec0:0:0:bebb::5
192.168.25.6
With Linux, you need to specify query AAAA record:
guy@seeker:~$ nslookup -q=aaaa zz87lhfda88.com
Server: 192.168.25.5
Address: 192.168.25.5#53
zz87lhfda88.com has AAAA address fec0:0:0:bebb::5
[1] http://isc.sans.edu/diary.html?storyid=7930
[2] http://www.whitehats.ca/main/members/Seeker/seeker_sinkhole/Seeker_DNS_Sinkhole.html
[3] http://www.whitehats.ca/downloads/sinkhole/sinkhole.iso
[4] http://www.whitehats.ca/downloads/sinkhole/sinkhole64-bit.iso
-----------
Guy Bruneau IPSS Inc. gbruneau at isc dot sans dot edu
Community SANS SEC 503 coming to Ottawa Sep 2011
Comments