Last Updated: 2007-04-11 11:14:05 UTC
by Swa Frantzen (Version: 2)
Overview of the April 2007 Microsoft patches and their status.
Note there was an out of cycle patch for the ANI vulnerability that we reported on earlier and that same patch is included here once again for completeness.
out of cycle
|Multiple vulnerabilities, leading to privilege escalation, DoS and remote code execution.
Replaces MS06-001 and MS05-053 and MS05-002 on windows 2003
Realtek HD audio control panel and more
|Remote code execution and XSS scripting
|MCMS (Microsoft Content Management Server)
|No known exploits
|Memory corruption leading to remote code execution
|UPnP (Universal Plug and Play)
|PoC available in for pay program
|URL parsing error leads to remote code execution
|No known exploits
|Multiple vulnerabilities leading to remote Code execution, privilege escalation and DoS
|CSRSS (Windows Client/Server Run-time Subsystem)
|Known exploits since Dec 15th, 2006.
|Race conditions leading to privilege escalation
|Details discussed publicly
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.
Swa Frantzen -- NET2S