Microsoft Black Tuesday - December 2006 overview
Overview of the December 2006 Microsoft patches and their status.
| # | Affected | Contra Indications | Known Exploits | Microsoft rating | ISC rating(*) | |
|---|---|---|---|---|---|---|
| clients | servers | |||||
| MS06-072 | Internet Explorer - remote code execution CVE-2006-5579 CVE-2006-5581 CVE-2006-5578 CVE-2006-5577 |
No known problems KB 925454 |
No known exploits |
Critical | Critical | Important |
| MS06-073 | Visual Studio 2005 - remote code execution CVE-2006-4704 |
No known problems KB 925674 |
Exploit publicly available |
Critical | PATCH NOW | Important |
| MS06-074 | SNMP - remote code execution - buffer overflow CVE-2006-5583 |
No known problems KB 926247 We are aware of a problem with a link in the advisory for Win2000 SP4 pointing to the MS06-078 fix. |
Exploit available in for pay program |
Important | Critical | Critical |
| MS06-075 | csrss - privilege escalation CVE-2006-5585 |
No known problems KB 926255 |
No known exploits |
Important | Important | Important |
| MS06-076 | Outlook express - remote code execution CVE-2006-2386 |
No known problems KB 923694 |
No known exploits | Important |
Important |
Less Urgent |
| MS06-077 | RIS - remote code execution CVE-2006-5584 |
No known problems KB 926121 |
No known exploits | Important | Important | Important |
| MS06-078 | Windows Media player - remote code execution CVE-2006-4702 CVE-2006-6134 |
No known problems KB 923689 KB 925398 |
Exploits available for the .asx vulnerability |
Critical | PATCH NOW | Important |
| Re-release MS06-059 |
Excel CVE-2006-2387 CVE-2006-3431 CVE-2006-3867 CVE-2006-3875 |
No known problems KB 924164 Fixes installation failures in Excel 2002 |
Exploits are publicly available |
Critical | Critical | Less Urgent |
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
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.
--
Swa Frantzen -- Section 66
×
![modal content]()
Diary Archives
Comments