Last Updated: 2009-11-10 22:11:09 UTC
by Swa Frantzen (Version: 1)
Overview of the November 2009 Microsoft patches and their status.
|#||Affected||Contra Indications||Known Exploits||Microsoft rating||ISC rating(*)|
|MS09-063||Random code execution due to a memory corruption vulnerability in a service for working with PDAs. Only affects Vista and Server 2008. This service listens on ports TCP port 5357 and 5358 and outbound UDP port 3702 and is enabled when a user browses for devices on their network.|
|KB 973565||No known exploits.||Severity:Critical
|MS09-064||Random code execution due to an input validation failure. Only affects Windows 2000. This license server is enabled by default, it uses RPC over TCP ports 139 and 445.|
|License logging Server
|KB 974783||No known exploits.||Severity:Critical
|MS09-065||Multiple vulnerabilities allow random code execution or privilege escalation.
|KB 969947||No known exploits, part of the vulnerability in CVE-2009-2514 was made public.||Severity:Critical
|MS09-066||Denial of Service vulnerability in the LSASS service. This uses TCP ports 389, 636, 3268, 3269
Replaces MS09-021 and MS09-035.
|KB 973309||No known exploits.||Severity:Important
Multiple vulnerabilities allow random code execution.
|KB 972652||No known exploits.||Severity:Important
An input validation vulnerability allows random code execution.
|KB 976307||No known exploits||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
Swa Frantzen -- Section 66