Microsoft October 2009 Black Tuesday Overview

Published: 2009-10-13
Last Updated: 2009-10-13 21:08:21 UTC
by Johannes Ullrich (Version: 1)
5 comment(s)

Overview of the October 2009 Microsoft patches and their status.

# Affected Contra Indications Known Exploits Microsoft rating ISC rating(*)
clients servers
MS09-050 Vulnerabilities in SMBv2 Could Allow Remote Code Execution (Vista and Windows Server 2008 SP2 only)
SMBv2
CVE-2009-2526
CVE-2009-2532
CVE-2009-3103
KB 975517
first mentioned in
 KB 975497
 CVE-2009-3103 is
publicly known!
  see our diary here.
Severity:Critical
Exploitability:3,1,1
Critical Critical
 MS09-051 Vulnerabilities in Windows Media Runtime Could Allow Remote Code Execution
Windows Media Runtime
CVE-2009-0555
CVE-2009-2525
KB 975682 CVE-2009-0555 known
publically
Severity:Critical
Exploitability:1,2
Critical Important
 MS09-052 Vulnerability in Windows Media Player Could Allow Remote Code Execution
Replaces MS08-076
Windows Media Format
CVE-2009-2527
KB 974112 No known exploits. Severity:Critical
Exploitability:1
Critical Critical
MS09-053 Vulnerabilities in FTP Service for Internet Information Services Could Allow Remote Code Execution
IIS FTP Service
CVE-2009-2521
CVE-2009-3023
KB 975254 Exploits Known for both
vulnerabilities!
Severity:Important
Exploitability:3,1
Important Critical
 MS09-054 Cumulative Security Update for Internet Explorer
Replaces MS09-034
Internet Explorer
CVE-2009-1547
CVE-2009-2529
CVE-2009-2530
CVE-2009-2531
KB 974455 Exploits known for
CVE-2009-2529
Severity: Critical
Exploitability: 2,1,2,2
Critical Critical
 MS09-055 Cumulative Secuirty Update of ActiveX Kill Bits
Replaces MS09-032
ActiveX Killbits
CVE-2009-2493
KB 973525 No known exploits. Severity:Critical
Exploitability: N/A
Critical Important
 MS09-056 Vulnerabiliites in Windows CryptoAPI Could Allow Spoofing
Replaces MS04-007
Windows CryptoAPI
CVE-2009-2510
CVE-2009-2511
KB 974571 publically known
(NULL exploits)
Severity:Important
Exploitability:3,3
Critical Important
 MS09-057 Vulnerability in Indexing Service could allow remote code execution if user browses to a malicious page.
Replaces MS06-053
Indexing Service
CVE-2009-2507
KB 969059 No known exploits. Severity:Important
Exploitability:2
Critical Important
 MS09-058 Vulnerability in Windows Kernel could allow privilege escalation.
Replaces MS06-022 and MS08-064
Windows Kernel
CVE-2009-2515
CVE-2009-2516
CVE-2009-2517
KB 971486 No known exploits. Severity:Important
Exploitability:2,3,3
Important Important
 MS09-059 Vulnerability in Local Security Authority Subsystem Service Could Allow Denial of Service
LSASS
CVE-2009-2524
KB 975467 No known exploits. Severity:Important
Exploitability:3
Important Important
  MS09-060

Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Office Remote Code Execution
Replaces MS08-015

Active Template Library
CVE-2009-0901
CVE-2009-2493
CVE-2009-2495

KB 973965 No known exploits. Severity:Critical
Exploitability:2
Critical Important
 MS09-061

Vulnerabiliites in the Microsoft .NET Common Language Runtime Could Allow Remote Code Execution
Replaces MS07-040

 .Net Runtime / Silverlight
CVE-2009-0090
CVE-2009-0091
CVE-2009-2497

KB 974378 CVE-2009-2497
is public.
Severity:Critical
Exploitability:1,1,1
Critical Critical
MS09-062 Multiple vulnerabilities allow arbitrary code execution. This affect windows, Office (including the viewer), SQLserver and various developer tools. Also affects Forefront Client Security on Windows 2000 SP 4.
Replaces MS08-052.
GDI+
CVE-2009-2500
CVE-2009-2501
CVE-2009-2502
CVE-2009-2503
CVE-2009-2504
CVE-2009-2518
CVE-2009-2528
CVE-2009-3126
KB 957488 No publicly known exploits. Severity:Critical
Exploitability:2,2,2,1,2,2,1,2
Critical Critical
We will update issues on this page for about a week or so 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

------
Johannes B. Ullrich, Ph.D.
SANS Technology Institute
Twitter

5 comment(s)

Comments

Does anyone know for sure that if the Msoft "fix" was applied, that it needs to be removed before deploying the new patch for SMBv2?

Thanks!
Does anyone know for sure that if the Msoft "fix" was applied, that it needs to be removed before deploying the new patch for SMBv2?

Thanks!
Do NOT Apply KB974571 to LCS/OCS Servers

Currently an issue is being observed after applying KB974571 (MS09-056: Vulnerabilities in CryptoAPI could allow spoofing) to LCS/OCS servers, that is causing them to believe that they are running an evaluation version of LCS/OCS and that it has expired.

Full details here: http://blogs.technet.com/dodeitte/archive/2009/10/13/do-not-apply-kb974571-to-lcs-ocs-servers.aspx

and here: http://projectdream.org/wordpress/2009/10/13/kb974571-crypto-api-update-may-break-office-communications-server-2007-r2-installations/
MemphisBytes: I asked the same question about the workarounds in the MS Server Security Forum.
http://social.technet.microsoft.com/Forums/en-US/winserversecurity/threads

So far only one response:

Vadims Podans MVP


you will need to revert these changes manually.[http://www.sysadmins.lv]
As always enjoy the automation of tools within the Windows-based, .NET aware, WPF accessible, multi-processes on the same IP / Port usage, admin's automation tool, powershell.exe! © Flowering Weeds
Microsoft released fix for crypto patch

http://support.microsoft.com/kb/974571

additional info here:

http://www.h-online.com/security/news/item/Microsoft-releases-fix-for-crypto-patch-846346.html

Diary Archives