Last Updated: 2008-10-14 22:43:03 UTC
by Swa Frantzen (Version: 1)
Overview of the October 2008 Microsoft patches and their status.
|#||Affected||Contra Indications||Known Exploits||Microsoft rating||ISC rating(*)|
|MS08-056||Cross site scripting (XSS) in the way Office XP SP3 handles the dialog window for the content-disposition:download and the cdo: protocol.|
|KB 957699||No publicly known exploits||Moderate||Important||Less Urgent|
|MS08-057||Multiple vulnerabilities in Excel lead to random code execution. This also affect sharepoint server.
|KB 956416||No publicly known exploits||Critical||Critical||Critical
|MS08-058||Multiple vulnerabilities in MSIE lead to random code execution and or information leaks.
|KB 956390||CVE-2008-2947 is publicly known||Critical||Critical||Important|
|MS08-059||RPC requests can bypass authentication and lead to random code execution.|
|Host Integration Server (HIS)
||No publicly known exploits||Critical||Important||Critical|
|Windows active directory
|KB 957280||No publicly known exploits||Critical||N/A||Critical|
|MS08-061||Multiple vulnerabilities in the windows kernel allow privilege escalation.
|KB 954211||No publicly known exploits||Important||Important||Important
|Windows internet printing (IIS)
|KB 953155||Actively exploited in targeted attacks||Important||Less Urgent (****)||Critical|
|MS08-063||Crafted filenames lead to random code execution in the SMB protocol.
|Windows file sharing
|KB 957095||No publicly known exploits||Important||Important||Critical|
Replaces MS07-066, MS07-022 and Advisory 932596.
|Windows virtual address descriptor
|KB 956841||No publicly known exploits||Important||Important||Important|
|MS08-065||An input validation failure in an RPC of MSQS allows random code execution.|
|Windows 2000 message queuing
|KB 951071||No publicly known exploits||Important||Important||Important|
|MS08-066||An input validation failure allows privilege escalation.|
|Windows ancillary function driver
|KB 956803||No publicly known exploits||Important||important||Less Urgent
|Killbits for 3rd party (Microgaming, System Requirements Lab, PhotostockPro) as well as Microsoft ActiveX controls mentioned in MS02-044, MS08-017, MS08-041 and MS08-052.|
|IE Active X killbits
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.
(**): For sharepoint servers. Important for others.
(***): for shared servers this is most likely critical.
(****): assuming no IIS was installed.
Swa Frantzen -- Section 66