Threat Level: green Handler on Duty: Johannes Ullrich

SANS ISC: InfoSec Handlers Diary Blog - Microsoft Patches - January 2007 - overview InfoSec Handlers Diary Blog

Sign Up for Free!   Forgot Password?
Log In or Sign Up for Free!

Microsoft Patches - January 2007 - overview

Published: 2007-01-09
Last Updated: 2007-01-18 19:21:08 UTC
by Swa Frantzen (Version: 8)
0 comment(s)

Overview of the January 2007 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS07-001 Remote code execution in Office 2003 Brazilian grammar checker. Read more...
Office 2003

No known problems

KB 921585
Exploit publicly available
Important Critical Important
MS07-002 Multiple remote code execution vulnerabilities in Excel. Affects the viewer and the mac versions as well.

Updated to fix an issue with certain Asian localized versions

KB 927198
KB 931183
No known exploits
Critical Critical Important
MS07-003 Multiple remote code execution vulnerabilities in Outlook

No known problems

KB 925938

Intentionally disables .oss functionality: KB 925542
DoS exploit publicly known
Critical Critical Important
MS07-004 Remote code execution in VML. Replaces MS06-055.
VML: IE and Outlook

No known problems

KB 929969
Multiple exploits publicly available and actively used.
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.

Swa Frantzen -- Section 66

Keywords: mspatchday
0 comment(s)
Diary Archives