Last Updated: 2011-07-13 15:07:26 UTC
by Swa Frantzen (Version: 2)
Overview of the July 2011 Microsoft patches and their status.
|#||Affected||Contra Indications - KB||Known Exploits||Microsoft rating(**)||ISC rating(*)|
|MS11-053||Memory handling problems in the bluetooth driver allow remote attackers to control the affected systems.|
|KB 2566220||No publicly known exploits||Severity:Critical
|MS11-054||Multiple vulnerabilities in kernel mode drivers allow privilege escalations.
Replaces MS11-034 and MS11-041.
|Kernel mode drivers
No publicly known exploits at the time of release of the patch.
|MS11-055||Search path for libraries allow random code execution (e.g. by opening a visio file on a network share).|
|KB 2560847||Exploit code publicly available since August 2010||Severity:Important
|MS11-056||Multiple vulnerabilities in the Client/Server Run-time SubSystem allow privilege escalation and denial of service on affected systems.
Replaces MS11-010 and MS10-069.
|KB 2507938||Exploit details for CVE-2011-1281 have been made public since the release of the patch.||Severity: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.
Swa Frantzen -- Section 66