February Black Tuesday Overview

Overview of the February 2008 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS08-003 Vulnerability in Active Directory Could Allow Denial of Service.
Replaces MS07-039.
Active Directory


KB 946538

No publicly known exploits Important Important Important
MS08-004 Vulnerability in Windows TCP/IP Could Allow Denial of Service
Replaces MS08-001.
TCP/IP Stack

KB 946456
No publicly known exploits Important Important Less urgent
MS08-005 Vulnerability in IIS Handling File Change Notifications Could Allow Privilege Elevation

KB 942831
No publicly known exploits Important Important Critical(**)
MS08-006 Vulnerability in IIS Handling of HTML-encoded ASP Web Pages Could Allow Remote Code Execution
Replaces MS06-034.

KB 942830
No publicly known exploits Important Important Critical(***)
MS08-007 Vulnerability in WebDAV Mini-Redirector Could Allow Remote Code Execution

KB 946026
No publicly known exploits Critical Critical Important
MS08-008 Vulnerability in Microsoft OLE Could Allow Remote Code Execution

KB 943055
No publicly known exploits Critical Critical Important
MS08-009 Vulnerability in Microsoft Word Could Allow Remote Code Execution.
Replaces Replaces MS07-060 and Replaces MS07-024.

KB 947077
No publicly known exploits Critical Critical Important
MS08-010 Cumulative Security Update for Internet Explorer
Replaces MS07-069.

KB 944533
Exploit publicly available Critical PATCH NOW Important
MS08-011 Vulnerabilities in Microsoft Works File Converter Could Allow Remote Code Execution

KB 947081
No publicly known exploits Important Critical Important
MS08-012 Vulnerabilities in Microsoft Office Publisher Could Allow Remote Code Execution.
Replaces MS06-054.
Office Publisher

KB 947085
No publicly known exploits Critical Critical Critical
MS08-013 Vulnerabilities in Microsoft Office Could Allow Remote Code Execution.
Replaces MS06-047. and MS07-060.

KB 947108
No publicly known exploits Critical Critical Critical


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.

(**): Mainly due to shared webservers being very affected by this

(***): Mainly due to classic ASP being used on many web servers like shared hosting providers

Swa Frantzen -- Gorilla Security


760 Posts
Feb 12th 2008
Just a more or less interessting sidenote:
The missing update beeing announced in the Advance Notice but not delivered (due to some qualitiy issues) was one for JavaScript and VBScript 5.6 coming with "Windows Script 5.6" on Windows 2000, Windows XP and Windows Server 2003. Not releasing the update dosn't fix the (AFAIK) yet undisclosed security holes anyway.
After digging around a little bit I've received confirmation by MS PSS, that the security holes are not present in Windows Script 5.7 which hasn't offered via Windows/Auto Update but is available for manual download in MS' DownloadCenter. So in case you want to be save from the yet unfixed security hole, you can fix them yourself by downloading Windows Script 5.7 (which is included in Windows Vista already) from the following links:
for Windows XP,
Windows Server 2003
and Windows 2000

and included in Windows Vista.

Sign Up for Free or Log In to start participating in the conversation!