Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS09-028 - Critical

Vulnerabilities in Microsoft DirectShow Could Allow Remote Code Execution (971633)

Published: July 14, 2009 | Updated: August 19, 2009

Version: 2.0

General Information

Executive Summary

This security update resolves one publicly disclosed vulnerability and two privately reported vulnerabilities in Microsoft DirectShow. The vulnerabilities could allow remote code execution if a user opened a specially crafted QuickTime media file. An attacker who successfully exploited any of these vulnerabilities could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the way that DirectShow parses QuickTime media files and validates pointer values and size fields within QuickTime media files. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This security update also addresses the vulnerability first described in Microsoft Security Advisory 971778.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. Microsoft Knowledge Base Article 971633 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Operating SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
DirectX 7.0
Microsoft Windows 2000 Service Pack 4DirectX 7.0Remote Code ExecutionCriticalMS08-033
DirectX 8.1
Microsoft Windows 2000 Service Pack 4DirectX 8.1*Remote Code ExecutionCriticalMS09-011
DirectX 9.0
Microsoft Windows 2000 Service Pack 4DirectX 9.0**Remote Code ExecutionCriticalMS09-011
Windows XP Service Pack 2 and Windows XP Service Pack 3DirectX 9.0**Remote Code ExecutionCriticalMS09-011
Windows XP Professional x64 Edition Service Pack 2DirectX 9.0**Remote Code ExecutionCriticalMS09-011
Windows Server 2003 Service Pack 2DirectX 9.0**Remote Code ExecutionCriticalMS09-011
Windows Server 2003 x64 Edition Service Pack 2DirectX 9.0**Remote Code ExecutionCriticalMS09-011
Windows Server 2003 with SP2 for Itanium-based SystemsDirectX 9.0**Remote Code ExecutionCriticalMS09-011

*The update for DirectX 8.1 also applies to DirectX 8.1b.

**The update for DirectX 9.0 also applies to DirectX 9.0a, DirectX 9.0b, and DirectX 9.0c.

Non-Affected Software

Operating System
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2

Where are the file information details? 
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

I am using an older release of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the July bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareDirectX NULL Byte Overwrite Vulnerability - CVE-2009-1537DirectX Pointer Validation Vulnerability - CVE-2009-1538DirectX Size Validation Vulnerability - CVE-2009-1539Aggregate Severity Rating
DirectX 7.0
Microsoft Windows 2000 Service Pack 4 with DirectX 7.0Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
DirectX 8.1
Microsoft Windows 2000 Service Pack 4 with DirectX 8.1*Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
DirectX 9.0
Microsoft Windows 2000 Service Pack 4 with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Service Pack 2 and Windows XP Service Pack 3 with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Professional x64 Edition Service Pack 2 with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 Service Pack 2 with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 x64 Edition Service Pack 2 with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 with SP2 for Itanium-based Systems with DirectX 9.0**Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical

*The update for DirectX 8.1 also applies to DirectX 8.1b.

**The update for DirectX 9.0 also applies to DirectX 9.0a, DirectX 9.0b, and DirectX 9.0c.

A remote code execution vulnerability exists in the way that Microsoft DirectShow parses QuickTime media files. This vulnerability could allow code execution if a user opened a specially crafted QuickTime file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1537.

Mitigating Factors for DirectX NULL Byte Overwrite Vulnerability - CVE-2009-1537

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • All supported editions of Windows Vista and Windows Server 2008 are not affected by this issue.

Workarounds for DirectX NULL Byte Overwrite Vulnerability - CVE-2009-1537

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Disable the parsing of QuickTime content in quartz.dll

    To modify the registry key, follow these steps:

    Warning Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry as specified in the steps below before you edit it.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup1.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.
    6. Locate the following subkey:
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    7. On the File menu, click Export.
    8. In the Export Registry File dialog box, enter QuickTime_Parser_Backup2.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    9. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    Using a Managed Deployment Script

    1. Create a backup copy of the registry keys by using a managed deployment script that contains the following commands:

      For 32-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}

      For 64-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup1.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
      Regedit.exe /e QuickTime_Decoder_Backup2.reg
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    2. Next, save the following to a file with a .REG extension, such as Disable_QuickTime_Parser.reg:

      For 32-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]

      For 64-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
      [-HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
    3. Run the above registry script on the target machine with the following command from an elevated command prompt:
      Regedit.exe /s Disable_QuickTime_Parser.reg

    Impact of workaround. QuickTime content playback will be disabled.

    How to undo the workaround.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup.reg and click Open.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup1.reg and click Open.
    4. In the Import Registry File dialog box, select QuickTime_Parser_Backup2.reg and click Open.

    Using a Managed Deployment Script

    For 32-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup.reg

    For 64-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup1.reg
    Regedit.exe /s QuickTime_Parser_Backup2.reg

  • Modify the Access Control List (ACL) on quartz.dll

    To modify the ACL on quartz.dll to be more restrictive, follow these steps:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges):

    For 32-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N

    For 64-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N
    Echo y| cacls %WINDIR%\SYSWOW64\quartz.DLL /E /P everyone:N

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges)

    For 32-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone

    For 64-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone
    cacls %WINDIR%\SYSWOW64\quartz.dll /E /R everyone

  • Unregister quartz.dll

    To unregister this DLL, run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll
    Regsvr32.exe –u %WINDIR%\syswow64\quartz.dll

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround: Run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll
    Regsvr32.exe %WINDIR%\syswow64\quartz.dll

  • For non-multimedia folder types, the Windows shell attack vector can be mitigated by using Windows Classic Folders

    To change folder options:

    1. Click Start, click Control Panel, click Appearance and Themes, and then click Folder Options. Or, open any folder, such as My Documents, and on the Tools menu, click Folder Options.
    2. On the General tab, under Tasks, select Use Windows classic folders.

FAQ for DirectX NULL Byte Overwrite Vulnerability - CVE-2009-1537

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
The Microsoft DirectShow component does not properly parse specially crafted QuickTime media files.

What is DirectX? 
Microsoft DirectX is a feature of the Windows operating system. It is used for streaming media on Microsoft Windows operating systems to enable graphics and sound when playing games or watching video.

What is DirectShow? 
DirectX consists of a set of low-level Application Programming Interfaces (APIs) used by Windows programs for multimedia support. Within DirectX, the DirectShow technology performs client-side audio and video sourcing, manipulation and rendering.

Microsoft DirectShow is used for streaming media on Microsoft Windows operating systems. DirectShow is used for high-quality capture and playback of multimedia streams. It automatically detects and uses video and audio acceleration hardware when available, but also supports systems without acceleration hardware. DirectShow is also integrated with other DirectX technologies. Some examples of applications that you can create using DirectShow include DVD players, video editing applications, AVI to ASF converters, MP3 players, and digital video capture applications.

What is the QuickTime Movie Parser Filter? 
The QuickTime Movie Parser filter splits Apple QuickTime data into audio and video streams. It supports QuickTime 2.0 and earlier. It connects to a source filter such as the Async File Source filter or the URL File Source filter. The Parser uses the AVI Decompressor or QT Decompressor filter to decompress QuickTime files. The filter creates one output pin for the video stream and one output pin for the audio stream. For more information, see the MSDN article, QuickTime Movie Parser Filter.

This component has been removed from Windows Vista and later operating systems. It is available for use in the Microsoft Windows 2000, Windows XP, and Windows Server 2003 operating systems.

What might an attacker use the vulnerability to do? 
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

How could an attacker exploit the vulnerability? 
This vulnerability requires that a user open a specially crafted QuickTime file or receive specially crafted streaming content from a Web site or any application that delivers Web content.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted QuickTime file embedded in it to the user and by convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

Finally, if a specially crafted QuickTime file is placed in a folder or network share, simply hovering the mouse over the file is enough to cause the Windows shell to crash.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way that DirectShow parses QuickTime media files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
While the initial report was provided through responsible disclosure, the vulnerability was later disclosed publicly by a separate party. This security bulletin addresses the publicly disclosed vulnerability, as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.

A remote code execution vulnerability exists in the way that Microsoft DirectShow validates certain values when updating a pointer. This vulnerability could allow code execution if a user opened a specially crafted QuickTime file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1538.

Mitigating Factors for DirectX Pointer Validation Vulnerability - CVE-2009-1538

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • All supported editions of Windows Vista and Windows Server 2008 are not affected by this issue.

Workarounds for DirectX Pointer Validation Vulnerability - CVE-2009-1538

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Disable the parsing of QuickTime content in quartz.dll

    To modify the registry key, follow these steps:

    Warning Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry as specified in the steps below before you edit it.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup1.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.
    6. Locate the following subkey:
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    7. On the File menu, click Export.
    8. In the Export Registry File dialog box, enter QuickTime_Parser_Backup2.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    9. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    Using a Managed Deployment Script

    1. Create a backup copy of the registry keys by using a managed deployment script that contains the following commands:

      For 32-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}

      For 64-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup1.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
      Regedit.exe /e QuickTime_Decoder_Backup2.reg
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    2. Next, save the following to a file with a .REG extension, such as Disable_QuickTime_Parser.reg:

      For 32-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]

      For 64-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
      [-HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
    3. Run the above registry script on the target machine with the following command from an elevated command prompt:
      Regedit.exe /s Disable_QuickTime_Parser.reg

    Impact of workaround. QuickTime content playback will be disabled.

    How to undo the workaround.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup.reg and click Open.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup1.reg and click Open.
    4. In the Import Registry File dialog box, select QuickTime_Parser_Backup2.reg and click Open.

    Using a Managed Deployment Script

    For 32-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup.reg

    For 64-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup1.reg
    Regedit.exe /s QuickTime_Parser_Backup2.reg

  • Modify the Access Control List (ACL) on quartz.dll

    To modify the ACL on quartz.dll to be more restrictive, follow these steps:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges):

    For 32-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N

    For 64-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N
    Echo y| cacls %WINDIR%\SYSWOW64\quartz.DLL /E /P everyone:N

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges)

    For 32-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone

    For 64-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone
    cacls %WINDIR%\SYSWOW64\quartz.dll /E /R everyone

  • Unregister quartz.dll

    To unregister this DLL, run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll
    Regsvr32.exe –u %WINDIR%\syswow64\quartz.dll

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround: Run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll
    Regsvr32.exe %WINDIR%\syswow64\quartz.dll

  • For non-multimedia folder types, the Windows shell attack vector can be mitigated by using Windows Classic Folders

    To change folder options:

    1. Click Start, click Control Panel, click Appearance and Themes, and then click Folder Options. Or, open any folder, such as My Documents, and on the Tools menu, click Folder Options.
    2. On the General tab, under Tasks, select Use Windows classic folders.

FAQ for DirectX Pointer Validation Vulnerability - CVE-2009-1538

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
The Microsoft DirectShow component does not properly validate certain values when updating a pointer.

What is DirectX? 
Microsoft DirectX is a feature of the Windows operating system. It is used for streaming media on Microsoft Windows operating systems to enable graphics and sound when playing games or watching video.

What is DirectShow? 
DirectX consists of a set of low-level Application Programming Interfaces (APIs) used by Windows programs for multimedia support. Within DirectX, the DirectShow technology performs client-side audio and video sourcing, manipulation and rendering.

Microsoft DirectShow is used for streaming media on Microsoft Windows operating systems. DirectShow is used for high-quality capture and playback of multimedia streams. It automatically detects and uses video and audio acceleration hardware when available, but also supports systems without acceleration hardware. DirectShow is also integrated with other DirectX technologies. Some examples of applications that you can create using DirectShow include DVD players, video editing applications, AVI to ASF converters, MP3 players, and digital video capture applications.

What is the QuickTime Movie Parser Filter? 
The QuickTime Movie Parser filter splits Apple QuickTime data into audio and video streams. It supports QuickTime 2.0 and earlier. The input pin connects to a source filter such as the Async File Source filter or the URL File Source filter. The Parser uses the AVI Decompressor or QT Decompressor filter to decompress QuickTime files. The filter creates one output pin for the video stream and one output pin for the audio stream. For more information, see the MSDN article, QuickTime Movie Parser Filter.

This component has been removed from Windows Vista and later operating systems. It is available for use in the Microsoft Windows 2000, Windows XP, and Windows Server 2003 operating systems.

What might an attacker use the vulnerability to do? 
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

How could an attacker exploit the vulnerability? 
This vulnerability requires that a user open a specially crafted QuickTime file or receive specially crafted streaming content from a Web site or any application that delivers Web content.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted QuickTime file embedded in it to the user and by convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way that DirectShow validates values when updating a pointer.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A remote code execution vulnerability exists in the way that Microsoft DirectShow validates specific fields in QuickTime media files. This vulnerability could allow code execution if a user opened a specially crafted QuickTime file. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1539.

Mitigating Factors for DirectX Size Validation Vulnerability - CVE-2009-1539

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • All supported editions of Windows Vista and Windows Server 2008 are not affected by this issue.

Workarounds for DirectX Size Validation Vulnerability - CVE-2009-1539

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Disable the parsing of QuickTime content in quartz.dll

    To modify the registry key, follow these steps:

    Warning Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry as specified in the steps below before you edit it.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Locate the following subkey:
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    3. On the File menu, click Export.
    4. In the Export Registry File dialog box, enter QuickTime_Parser_Backup1.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    5. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.
    6. Locate the following subkey:
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    7. On the File menu, click Export.
    8. In the Export Registry File dialog box, enter QuickTime_Parser_Backup2.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    9. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry key via the Confirm Key Delete dialog box, click Yes.

    Using a Managed Deployment Script

    1. Create a backup copy of the registry keys by using a managed deployment script that contains the following commands:

      For 32-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}

      For 64-bit Windows systems:
      Regedit.exe /e QuickTime_Decoder_Backup1.reg
      HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
      Regedit.exe /e QuickTime_Decoder_Backup2.reg
      HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}
    2. Next, save the following to a file with a .REG extension, such as Disable_QuickTime_Parser.reg:

      For 32-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]

      For 64-bit Windows systems:
      Windows Registry Editor Version 5.00
      [-HKEY_CLASSES_ROOT\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
      [-HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D51BD5A0-7548-11CF-A520-0080C77EF58A}]
    3. Run the above registry script on the target machine with the following command from an elevated command prompt:
      Regedit.exe /s Disable_QuickTime_Parser.reg

    Impact of workaround. QuickTime content playback will be disabled.

    How to undo the workaround.

    Using the Interactive Method

    For 32-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup.reg and click Open.

    For 64-bit Windows systems:

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select QuickTime_Parser_Backup1.reg and click Open.
    4. In the Import Registry File dialog box, select QuickTime_Parser_Backup2.reg and click Open.

    Using a Managed Deployment Script

    For 32-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup.reg

    For 64-bit Windows systems, restore the original state by running the following command:

    Regedit.exe /s QuickTime_Parser_Backup1.reg
    Regedit.exe /s QuickTime_Parser_Backup2.reg

  • Modify the Access Control List (ACL) on quartz.dll

    To modify the ACL on quartz.dll to be more restrictive, follow these steps:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges):

    For 32-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N

    For 64-bit Windows systems:

    Echo y| cacls %WINDIR%\SYSTEM32\quartz.DLL /E /P everyone:N
    Echo y| cacls %WINDIR%\SYSWOW64\quartz.DLL /E /P everyone:N

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround:

    On Windows XP and Windows Server 2003 (all editions), run the following command from a command prompt (requires administrative privileges)

    For 32-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone

    For 64-bit Windows systems:

    cacls %WINDIR%\SYSTEM32\quartz.dll /E /R everyone
    cacls %WINDIR%\SYSWOW64\quartz.dll /E /R everyone

  • Unregister quartz.dll

    To unregister this DLL, run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe –u %WINDIR%\system32\quartz.dll
    Regsvr32.exe –u %WINDIR%\syswow64\quartz.dll

    Impact of workaround: Windows Media Player will not be able to play .AVI or .WAV files.

    How to undo the workaround: Run the following command from an elevated command prompt:

    For 32-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll

    For 64-bit Windows systems:

    Regsvr32.exe %WINDIR%\system32\quartz.dll
    Regsvr32.exe %WINDIR%\syswow64\quartz.dll

  • For non-multimedia folder types, the Windows shell attack vector can be mitigated by using Windows Classic Folders

    To change folder options:

    1. Click Start, click Control Panel, click Appearance and Themes, and then click Folder Options. Or, open any folder, such as My Documents, and on the Tools menu, click Folder Options.
    2. On the General tab, under Tasks, select Use Windows classic folders.

FAQ for DirectX Size Validation Vulnerability - CVE-2009-1539

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
The Microsoft DirectShow component does not properly validate certain size fields within QuickTime media files.

What is DirectX? 
Microsoft DirectX is a feature of the Windows operating system. It is used for streaming media on Microsoft Windows operating systems to enable graphics and sound when playing games or watching video.

What is DirectShow? 
DirectX consists of a set of low-level Application Programming Interfaces (APIs) used by Windows programs for multimedia support. Within DirectX, the DirectShow technology performs client-side audio and video sourcing, manipulation and rendering.

Microsoft DirectShow is used for streaming media on Microsoft Windows operating systems. DirectShow is used for high-quality capture and playback of multimedia streams. It automatically detects and uses video and audio acceleration hardware when available, but also supports systems without acceleration hardware. DirectShow is also integrated with other DirectX technologies. Some examples of applications that you can create using DirectShow include DVD players, video editing applications, AVI to ASF converters, MP3 players, and digital video capture applications.

What is the QuickTime Movie Parser Filter? 
The QuickTime Movie Parser filter splits Apple QuickTime data into audio and video streams. It supports QuickTime 2.0 and earlier. The input pin connects to a source filter such as the Async File Source filter or the URL File Source filter. The Parser uses the AVI Decompressor or QT Decompressor filter to decompress QuickTime files. The filter creates one output pin for the video stream and one output pin for the audio stream. For more information, see the MSDN article, QuickTime Movie Parser Filter.

This component has been removed from Windows Vista and later operating systems. It is available for use in the Microsoft Windows 2000, Windows XP, and Windows Server 2003 operating systems.

What might an attacker use the vulnerability to do? 
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

How could an attacker exploit the vulnerability? 
This vulnerability requires that a user open a specially crafted QuickTime file or receive specially crafted streaming content from a Web site or any application that delivers Web content.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted QuickTime file embedded in it to the user and by convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains specially crafted content that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

Finally, if a specially crafted QuickTime file is placed in a folder or network share, simply hovering the mouse over the file is enough to cause the Windows shell to crash.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way that DirectShow validates size fields within QuickTime media files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Note Starting August 1, 2009, Microsoft will discontinue support for Office Update and the Office Update Inventory Tool. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Office Update: Frequently Asked Questions.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA 2.1
Microsoft Windows 2000 Service Pack 4Yes
Windows XP Service Pack 2 and Windows XP Service Pack 3Yes
Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2003 with SP2 for Itanium-based SystemsYes

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

SoftwareSMS 2.0SMS 2003 with SUSFPSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Windows 2000 Service Pack 4NoNoYesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3NoNoYesYes
Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 2NoNoYesYes
Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionFor Microsoft Windows 2000 Service Pack 4 with DirectX 7.0:
Windows2000-KB971633-x86-ENU /quiet

For Microsoft Windows 2000 Service Pack 4 with DirectX 8.1 or DirectX 8.1b:
Windows2000-DirectX8-KB971633-x86-ENU /quiet

For Microsoft Windows 2000 Service Pack 4 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windows2000-DirectX9-KB971633-x86-ENU /quiet
Installing without restartingFor Microsoft Windows 2000 Service Pack 4 with DirectX 7.0:
Windows2000-KB971633-x86-ENU /norestart

For Microsoft Windows 2000 Service Pack 4 with DirectX 8.1 or DirectX 8.1b:
Windows2000-DirectX8-KB971633-x86-ENU /norestart

For Microsoft Windows 2000 Service Pack 4 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windows2000-DirectX9-KB971633-x86-ENU /norestart
Update log filekb971633.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the following folders:

For Microsoft Windows 2000 Service Pack 4 with DirectX 7.0:
%Windir%\$NTUninstallKB971633$\Spuninst

For Microsoft Windows 2000 Service Pack 4 with DirectX 8.1 or DirectX 8.1b:
%Windir%\$NTUninstallKB971633_DX8$\Spuninst

For Microsoft Windows 2000 Service Pack 4 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
%Windir%\$NTUninstallKB971633_DX9$\Spuninst
File InformationSee Microsoft Knowledge Base Article 971633
Registry Key VerificationFor Microsoft Windows 2000 Service Pack 4 with DirectX 7.0:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB971633\Filelist

For Microsoft Windows 2000 Service Pack 4 with DirectX 8.1 or DirectX 8.1b:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DirectX 8\SP0\KB971633_DX8\Filelist

For Microsoft Windows 2000 Service Pack 4 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DirectX 9.0\SP0\KB971633_DX9\Filelist

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/extract[:path]Extracts files without starting the Setup program.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsxp-kb971633-x86-enu /quiet
For all supported x64-based editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
WindowsServer2003.WindowsXP-kb971633-x64-enu /quiet
Installing without restartingFor all supported 32-bit editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsxp-kb971633-x86-enu /norestart
For all supported x64-based editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
WindowsServer2003.WindowsXP-kb971633-x64-enu /norestart
Update log fileKB971633.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB971633$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 971633
Registry Key VerificationFor all supported 32-bit editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB971633\Filelist
For all supported x64-based editions of Windows XP with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB971633\Filelist

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]Extracts files without starting the Setup program.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003-kb971633-x86-enu /quiet
For all supported x64-based editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003.WindowsXP-KB971633-x64-enu /quiet
For all supported Itanium-based editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003-KB971633-ia64-enu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003-kb971633-x86-enu /norestart
For all supported x64-based editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003.WindowsXP-KB971633-x64-enu /norestart
For all supported Itanium-based editions of Windows Server 2003 with DirectX 9.0, DirectX 9.0a, DirectX 9.0b, or DirectX 9.0c:
Windowsserver2003-KB971633-ia64-enu /norestart
Update log fileKB971633.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB971633$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 971633
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB971633\Filelist

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]Extracts files without starting the Setup program.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

  • V1.0 (July 14, 2009): Bulletin published.
  • V2.0 (August 19, 2009): Bulletin updated to reflect that the update for DirectX 8.1 also applies to DirectX 8.1b.

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.