Microsoft Black Tuesday Overview

Published: 2006-11-16. Last Updated: 2006-11-16 14:53:36 UTC
by Swa Frantzen (Version: 8)

Overview of the November 2006 Microsoft patches and their status.

#	Affected	Contra Indications	Known Exploits	Microsoft rating	ISC rating(*)
#	Affected	Contra Indications	Known Exploits	Microsoft rating	clients	servers
MS06-066	Netware client services - remote code execution & DoS CVE-2006-4688 CVE-2006-4689	No known problems KB 923980	PoC exploits available in for pay program	Important	Less Urgent	Less Urgent
MS06-067	Internet Explorer - remote code execution CVE-2006-4446 CVE-2006-4777 CVE-2006-4687	No known problems KB 922760	Actively exploited on websites in the wild websense	Critical	PATCH NOW	Important
MS06-068	Microsoft Agent - remote code execution CVE-2006-3445	No known problems KB 920213	No known exploits	Critical	Critical	Less Urgent
MS06-069	Adobe flash player - remote code execution CVE-2006-3014 CVE-2006-3311 CVE-2006-3587 CVE-2006-3588 CVE-2006-4640	No known problems KB 923789	No known exploits	Critical	Critical	Less Urgent
MS06-070	Workstation service - remote code execution CVE-2006-4691	No known problems KB 924270	Vulnerability details are public ; Exploit publicly available	Critical	Critical (**)	Critical (**)
MS06-071	XML Core services CVE-2006-5745	No known problems KB 928088 also: KB 927977 KB 927978	Exploits publicly available	Critical	PATCH NOW	Important

We will update issues on this page 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.

(**): Of the supported versions of windows this is mainly affecting Windows 2000. The vulnerability exists on Windows XP, to a lesser degree and seems to be absent from Windows 2003.

--
Swa Frantzen -- Section 66

Keywords: mspatchday

0 comment(s)

Internet Storm Center

Microsoft Black Tuesday Overview

Comments