Last Updated: 2011-02-09 21:20:21 UTC
by Joel Esler (Version: 5)
Here are the February 2011 Black Tuesday patches. Enjoy!
Overview of the February 2011 Microsoft Patches and their status.
|Cumulative Security Update for Internet Explorer (Replaces MS10-090 )
|Vulnerability in Internet Information Services (IIS) FTP Service Could Allow Remote Code Execution
|DoS Vulnerability in Active Directory (Replaces MS10-068 MS10-101 )
|Remote Code Execution Vulnerability in Windows Shell Graphics Processing (Replaces MS10-046 )
|Remote Code Execution Vulnerability in the OpenType Compact Font Format (CFF) Driver (Replaces MS10-091 )
|Open Type Compact Font Format Driver
|Remote Code Execution Vulnerabilities in Microsoft Visio (Replaces MS10-028 MS10-036 )
|Information Disclosure Vulnerability in JScript and VBScript Scripting Engines (Replaces MS10-022 )
|Privilege Elevation Vulnerability in Windows Client/Server Run-time Subsystem (Replaces MS10-011 )
|Privilege Elevation Vulnerabilities in Windows Kernel (Replaces MS10-021 MS10-047 )
|Privilege Elevation Vulnerabilities in Windows Kernel-Mode Drivers (Replaces MS10-098 )
|Windows Kernel-Mode Drivers
|Privilege Elevation Vulnerabilities in Kerberos (Replaces MS10-014 )
|Privilege Elevation Vulnerability in Local Security Authority Subsystem Service (Replaces MS08-002 )
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
We have been getting reports of people having issues applying MS11-003 (see comments). No doubt you are testing this in a test environment first anyway, but for this patch you may wish to double check. Errors of invalid hash and error code 0x80246002.
If you do have issues with your patches make sure you let Microsoft know via your support channel.
- Mark -