Threat Level: green Handler on Duty: Manuel Pelaez

SANS ISC InfoSec Handlers Diary Blog


Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!

March 2011 Microsoft Black Tuesday Summary

Published: 2011-03-08
Last Updated: 2011-03-08 18:17:20 UTC
by Jim Clausing (Version: 1)
2 comment(s)

Here are the March 2011 Black Tuesday patches.  Enjoy!
 

Overview of the March 2011 Microsoft Patches and their status.
 

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS11-015 Vulnerabilities in Windows Media Could Allow Remote Code Execution
DirectX
CVE-2011-0032
CVE-2011-0042
KB 2510030 PoC exists Severity:Critical
Exploitability: 1,1
Critical Important
MS11-016 Vulnerability in Microsoft Groove Could Allow Remote Code Execution
Microsoft Groove 2007 SP2
CVE-2010-3146
KB 2494047 PoC exists Severity:Important
Exploitability: 1
Important Less Urgent
MS11-017 Vulnerability in Remote Desktop Could Allow Remote Code Execution
Remote Desktop
CVE-2011-0029
KB 2508062 no known exploit Severity:Important
Exploitability: 1
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

---------------
Jim Clausing, GIAC GSE #26
jclausing --at-- isc [dot] sans (dot) edu

SANS SEC401 coming to central OH beginning 17 May, see http://www.sans.org/mentor/details.php?nid=24678

2 comment(s)
VMware ESX/ESXi security updates released, see http://www.vmware.com/security/advisories/VMSA-2011-0004.html
Diary Archives