Wednesday, May 11, 2011 9:14 AM
May 2011 Microsoft Black Tuesday Overview - SANS Internet Storm Center
Overview of the May 2011 Microsoft patches and their status.
||An input validation vulnerability in WINS allow arbitrary code execution with the rights of the WINS system.
Note: WINS is not installed by default.
||No known exploits
||Memory corruption and buffer overflow vulnerabilities allow for arbitrary code execution with the rights of the logged on user.
Note: Microsoft confirms in the bulletin that Office for
Mac versions 2004 and 2008 of Powerpoint are vulnerable, but no patch
is available at this point in time, nor is there an indication of a time
Note: Windows Office 2010 and Office for Mac 2011 are not affected.
||No known exploits
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.
Anything that needs little to become "interesting" for the dark side.
Best approach is to test and deploy ASAP. Workarounds can give more time
- 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
- 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
Swa Frantzen -- Section 66