• 59 minutes to read

Security Bulletin

Microsoft Security Bulletin MS09-051 - Critical

Vulnerabilities in Windows Media Runtime Could Allow Remote Code Execution (975682)

Published: October 13, 2009 | Updated: November 10, 2009

Version: 2.0

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Windows Media Runtime. The vulnerabilities could allow remote code execution if a user opened a specially crafted media file or received specially crafted streaming content from a Web site or any application that delivers Web content. An attacker who successfully exploited 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 DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on supported editions of Microsoft Windows 2000; Windows XP; Windows Server 2003, except for Itanium-based editions; Windows Vista; and Windows Server 2008, except for Itanium-based editions. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by changing the manner in which the Windows Media Runtime processes ASF files and initializes functions in compressed audio 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.

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. None

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 System Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows XP Service Pack 2 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows XP Service Pack 3 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows XP Professional x64 Edition Service Pack 2 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition
(KB954155)

Windows Media Audio Voice Decoder in Windows Media Format SDK 11
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows Server 2003 Service Pack 2 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows Server 2003 x64 Edition Service Pack 2 DirectShow WMA Voice Codec
(KB969878)

Windows Media Audio Voice Decoder
(KB954155)

Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition
(KB954155)

Audio Compression Manager
(KB975025)		 Remote Code Execution Critical None
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Windows Media Audio Voice Decoder
(KB954155)		 Remote Code Execution Critical None
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Windows Media Audio Voice Decoder
(KB954155)		 Remote Code Execution Critical None
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2\* Windows Media Audio Voice Decoder
(KB954155)		 Remote Code Execution Critical None
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2\* Windows Media Audio Voice Decoder
(KB954155)		 Remote Code Execution Critical None
**\*Windows Server 2008 Server Core installation not affected.** The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see [Server Core](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). **Non-Affected Software** | Operating System | |----------------------------------------------------------------------------------------------------------------| | Windows Server 2003 with SP2 for Itanium-based Systems | | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | | Windows 7 for 32-bit Systems | | Windows 7 for x64-based Systems | | Windows Server 2008 R2 for x64-based Systems | | Windows Server 2008 R2 for Itanium-based Systems | Frequently Asked Questions (FAQ) Related to This Security Update ---------------------------------------------------------------- **Why was this bulletin rereleased on November 10, 2009?**  Microsoft rereleased this bulletin to reoffer the update for Audio Compression Manager on Microsoft Windows 2000 Service Pack 4 to fix a detection issue. This is a detection change only; there were no changes to the binaries. Customers who have successfully updated their systems do not need to reinstall this update. **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. **How does this bulletin relate to MS09-052, Vulnerability in Windows Media Player Could Allow Remote Code Execution?**  This bulletin is not related to [MS09-052](http://go.microsoft.com/fwlink/?linkid=163913), Vulnerability in Windows Media Player Could Allow Remote Code Execution. Users should install both updates to ensure they are fully protected. **I have Windows Media Player installed on my system. Why am I not being offered some of the updates?** Systems will only be offered the updates automatically if you have installed Windows Media Player as well as the optional audio codecs affected by these vulnerabilities. The codecs associated with KB969878 are applicable to 32-bit systems only. The codecs associated with KB954155 are not installed on the x64-based Windows Media Format SDK, by default, but may be downloaded automatically through Windows Media Player or manually from the [Microsoft Download Center](http://www.microsoft.com/downloads/en/default.aspx). If you do not have the codecs installed and attempt to manually install the update, you may receive one of the following error messages: - Windows Media Player 9 is required to install this update. - Windows Media Format 9.5 SDK must be on your machine before this update can be installed. If you receive this message, this update does not apply to your system.  These messages will only occur if you attempt to manually install the update. **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. **What is the Windows Media Format Software Developers Kit (SDK)?**  The Windows Media Format SDK provides application developers with access to the components of the Windows Media Format. The primary purpose of the Windows Media Format SDK is to enable developers to create applications that play, write, edit, encrypt, and deliver Advanced Systems Format (ASF) files and network streams. These files and streams commonly contain audio and video content encoded using the Windows Media Audio and Video codecs. However, ASF can contain any type of data. For more information, see the [Windows Media Format SDK Technology Page](http://msdn.microsoft.com/en-us/windows/bb190326.aspx). **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](http://go.microsoft.com/fwlink/?linkid=21742). 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](http://go.microsoft.com/fwlink/?linkid=21742). For more information about the extended security update support period for these software versions or editions, visit [Microsoft Product Support Services](http://go.microsoft.com/fwlink/?linkid=33328). 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](http://go.microsoft.com/fwlink/?linkid=33329), 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](http://go.microsoft.com/fwlink/?linkid=33330). ### Vulnerability Information Severity Ratings and Vulnerability Identifiers ---------------------------------------------- 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 [October bulletin summary](http://technet.microsoft.com/security/bulletin/ms09-oct). For more information, see [Microsoft Exploitability Index](http://technet.microsoft.com/en-us/security/cc998259.aspx).
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Windows Media Runtime Voice Sample Rate Vulnerability - CVE-2009-0555 Windows Media Runtime Heap Corruption Vulnerability - CVE-2009-2525 Aggregate Severity Rating
DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on Microsoft Windows 2000 Service Pack 4 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on Windows XP Service Pack 2 and Windows XP Service Pack 3 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on Windows XP Professional x64 Edition Service Pack 2 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on Windows Server 2003 Service Pack 2 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
DirectShow WMA Voice Codec, Windows Media Audio Voice Decoder, and Audio Compression Manager on Windows Server 2003 x64 Edition Service Pack 2 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
Windows Media Audio Voice Decoder on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
Windows Media Audio Voice Decoder on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
Windows Media Audio Voice Decoder on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2\* Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
Windows Media Audio Voice Decoder on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2\* Critical 
Remote Code Execution		 Critical 
Remote Code Execution		 Critical
**\*Windows Server 2008 Server Core installation not affected.** The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see [Server Core](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). Windows Media Runtime Voice Sample Rate Vulnerability - CVE-2009-0555 --------------------------------------------------------------------- A remote code execution vulnerability exists in Windows Media Player due to the improper processing of specially crafted Advanced Systems Format (ASF) files. An attacker could exploit the vulnerability by constructing a specially crafted audio file that could allow remote code execution when played using an affected version of Windows Media Player. An attacker who successfully exploited this vulnerability could take complete control of an affected system. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2009-0555](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-0555). #### Mitigating Factors for Windows Media Runtime Voice Sample Rate Vulnerability - CVE-2009-0555 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: - 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. - 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 affected than users who operate with administrative user rights. - Windows Server 2008 is not affected unless the optional Desktop Experience component is also installed. #### Workarounds for Windows Media Runtime Voice Sample Rate Vulnerability - CVE-2009-0555 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: - **Unregister wmspdmod.dll** To unregister this DLL, run the following command from an elevated command prompt. For 32-bit Windows systems: `Regsvr32.exe –u %WINDIR%\system32\wmspdmod.dll` For x64-based Windows systems: `Regsvr32.exe –u %WINDIR%\syswow64\wmspdmod.dll` **Impact of workaround.** Audio streams in ASF files that use the Windows Media Speech Code will fail to play. **How to undo the workaround.** Run the following command from an elevated command prompt. For 32-bit Windows systems: `Regsvr32.exe %WINDIR%\system32\wmspdmod.dll` For x64-based Windows systems: `Regsvr32.exe %WINDIR%\syswow64\wmspdmod.dll` #### FAQ for Windows Media Runtime Voice Sample Rate Vulnerability - CVE-2009-0555 **What is the scope of the vulnerability?**  This is a remote code execution vulnerability. 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. **What causes the vulnerability?**  The Windows Media Runtime incorrectly processes specially crafted ASF files that make use of the Window Media Speech codec. **What is Windows Media Format Runtime?**  The Microsoft Windows Media Format Runtime provides information and tools for applications that use Windows Media content. **What is Advanced Systems Format (ASF)?**  ASF (Advanced Systems Format) is a file format that stores audio and video information and is specially designed to run over networks like the Internet. It is a compressed format that can contain streaming audio, video, slide shows, and synchronized events. ASF enables content to be delivered to you as a continuous flow of data. ASF files may have the file extension ASF, WMV, or WMA. ASF refers to the underlying format of the audio file. ASF files can have many different file extensions with the most common being WMA and WMV. ASF files may also be delivered with other file extensions, such as MP3, which do not reflect the true file format. Windows Media Player will analyze the actual file format and still attempt to play the file. **What is Windows Media Audio Voice Decoder?**  The Windows Media Audio Voice decoder decodes streams that were encoded by the [Windows Media Audio Encoder](http://msdn.microsoft.com/en-us/library/dd756600(vs.85).aspx). The Windows Media Audio Voice codec provides low bit-rate compression optimized for audio containing speech. The ability of the codec to produce such small samples is due to the limited frequency range of the sounds of the human voice. This optimization means that a dedicated voice encoder creates poor-quality output for content that contains more complicated sounds, like music. However, the Windows Media Audio Voice codec compensates for this potential quality issue by providing separate modes for voice, music, and mixed content. The codec analyzes mixed content to determine which mode to use for each portion of the file. For more information about the Windows Media Audio Decoder, see the MSDN article, [Using the Windows Media Audio Voice Codec](http://msdn.microsoft.com/en-us/library/dd443456(vs.85).aspx). **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could run arbitrary code. 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 ASF file with an affected version of Windows Media Player. In a Web-based attack scenario, an attacker would have to host a specially crafted ASF file that is used to attempt to 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. In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a media file with a specially crafted ASF file embedded in it to the user and by convincing the user to open the file. **What systems are primarily at risk from the vulnerability?**  Any system using Windows Media Runtime, such as workstations or terminal servers, is at risk from this vulnerability. **What does the update do?**  The update addresses this vulnerability by changing the manner in which the Windows Media Runtime processes ASF files. **When this security bulletin was issued, had this vulnerability been publicly disclosed?**  Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number [CVE-2009-0555](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-0555). **When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?**  Yes. Microsoft is aware of limited attacks attempting to exploit the vulnerability. Windows Media Runtime Heap Corruption Vulnerability - CVE-2009-2525 ------------------------------------------------------------------- A remote code execution vulnerability exists in the way that Microsoft Windows Media Runtime handles certain functions in compressed audio files. This vulnerability could allow remote code execution if a user opened a specially crafted 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-2525](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-2525). #### Mitigating Factors for Windows Media Runtime Heap Corruption Vulnerability - CVE-2009-2525 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: - 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. - 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 affected than users who operate with administrative user rights. - Windows Server 2008 is not affected unless the optional Desktop Experience component is also installed. #### Workarounds for Windows Media Runtime Heap Corruption Vulnerability - CVE-2009-2525 - **Deny access to msaud32.acm** On Windows 2000, Windows XP, and Windows Server 2003 systems: For 32-bit Windows systems: `Echo y| cacls %WINDIR%\system32\msaud32.acm /E /P everyone:N` For 64-bit Windows systems: `Echo y| cacls %WINDIR%\syswow64\msaud32.acm /E /P everyone:N` On Windows Vista and Windows Server 2008: Run the following commands from a command prompt as an administrator: For 32-bit Windows: `Takeown.exe /f "%windir%\system32\msaud32.acm"` `Icacls.exe "%windir%\system32\msaud32.acm " /save %TEMP%\msaud32_acm.TXT` `Icacls.exe "%windir%\system32\msaud32.acm " /deny everyone:(F)` For 64-bit Windows systems: `Takeown.exe /f "%windir%\syswow64\msaud32.acm"` `Icacls.exe "%windir%\syswow64\msaud32.acm " /save %TEMP%\ msaud32_acm.TXT` `Icacls.exe "%windir%\syswow64\msaud32.acm " /deny everyone:(F)` **Impact of workaround:** Applications that rely on the Audio Compression Manager (ACM) will fail to render content properly **How to undo the workaround:** On Windows 2000, Windows XP, and Windows Server 2003 systems: For 32-bit Windows systems: `cacls “%WINDIR%\system32\msaud32.acm” /E /R everyone` For 64-bit Windows systems: `cacls “%WINDIR%\syswow64\msaud32.acm” /E /R everyone` On Windows Vista and Windows Server 2008: Run the following commands from a command prompt as an administrator: For 32-bit Windows: `icacls %windir%\syswow64 /restore %TEMP%\msaud32_acm.TXT` For 64-bit Windows systems: `icacls %windir%\syswow64 /restore %TEMP%\msaud32_acm.TXT` #### FAQ for Windows Media Runtime Heap Corruption Vulnerability - CVE-2009-2525 **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 Windows Media Runtime does not properly initialize certain functions in compressed audio files. **What is Windows Media Format Runtime?**  The Microsoft Windows Media Format Runtime provides information and tools for applications that use Windows Media content. **What is the Audio Compression Manager?**  The Audio Compression Manager (ACM) adds system-level support for transparent run-time audio compression and decompression and Waveform audio data processing. The ACM uses existing driver interface hooks to override the default mapping algorithm for waveform audio devices. This allows the ACM to intercept device-open calls. After a call has been intercepted, the ACM can perform a variety of tasks to process the audio data, such as inserting an external compressor or decompressor into the sequence. For more information about the ACM, see MSDN article, [About the Audio Compression Manager](http://msdn.microsoft.com/en-us/library/dd742878(vs.85).aspx). **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. 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. **How could an attacker exploit the vulnerability?**  Exploitation of this vulnerability requires that a user open a specially crafted media file or receive specially crafted streaming content from a Web site or any application that delivers Web content. **What systems are primarily at risk from the vulnerability?**  Any system using Windows Media Player, such as workstations or terminal servers, is at risk from this vulnerability. **What does the update do?**  The update addresses the vulnerability by correcting the manner in which Windows Media Runtime initializes function in compressed audio 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 Detection and Deployment Tools and Guidance ------------------------------------------- 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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) and [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). 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](http://go.microsoft.com/fwlink/?linkid=96155). 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](http://go.microsoft.com/fwlink/?linkid=97900). **Note** Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747). For more information, see [About Microsoft Office Update: Frequently Asked Questions](http://office.microsoft.com/en-us/downloads/fx010402221033.aspx). **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](http://support.microsoft.com/kb/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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.1 | |-------------------------------------------------------------------------------------------------------------------|----------| | Microsoft Windows 2000 Service Pack 4 | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | | Windows XP Professional x64 Edition Service Pack 2 | Yes | | Windows Server 2003 Service Pack 2 | Yes | | Windows Server 2003 x64 Edition Service Pack 2 | Yes | | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Yes | | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | For more information about MBSA 2.1, see [MBSA 2.1 Frequently Asked Questions](http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx). **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](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 with SUIT | SMS 2003 with ITMU | Configuration Manager 2007 | |-------------------------------------------------------------------------------------------------------------------|---------|--------------------|----------------------------------------------------------------------|----------------------------| | Microsoft Windows 2000 Service Pack 4 | No | No | Yes | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | No | No | Yes | Yes | | Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | No | No | See **Note for Windows** **Vista** **and Windows Server 2008** below | Yes | | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | No | No | See **Note for Windows** **Vista** **and Windows Server 2008** below | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | See **Note for Windows** **Vista** **and Windows Server 2008** below | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | See **Note for Windows** **Vista** **and Windows Server 2008** below | Yes | For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also [Downloads for Systems Management Server 2.0](http://technet.microsoft.com/en-us/sms/bb676799.aspx). 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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). For more information about SMS scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). 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](http://technet.microsoft.com/en-us/library/bb735860.aspx). **Note for Windows** **Vista** **and Windows Server 2008** Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability. For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/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](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). 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. Security Update Deployment -------------------------- **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 Packs The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention For DirectShow WMA Voice Codec when installed on Microsoft Windows 2000 Service Pack 4:
WindowsMedia9-KB969878-x86-ENU /quiet
For Windows Media Audio Voice Decoder when installed on Microsoft Windows 2000 Service Pack 4:
Windows2000-WindowsMedia-KB954155-x86-ENU /quiet
For Audio Compression Manager when installed on Microsoft Windows 2000 Service Pack 4:
Windows2000-WindowsMedia-KB975025-v2-x86-ENU /quiet
Installing without restarting For DirectShow WMA Voice Codec when installed on Microsoft Windows 2000 Service Pack 4:
WindowsMedia9-KB969878-x86-ENU /norestart
For Windows Media Audio Voice Decoder when installed on Microsoft Windows 2000 Service Pack 4:
Windows2000-WindowsMedia-KB954155-x86-ENU /norestart
For Audio Compression Manager when installed on Microsoft Windows 2000 Service Pack 4:
Windows2000-WindowsMedia-KB975025-v2-x86-ENU /norestart
Update log file kb969878.log, kb954155.log, or kb975025.log
Further information See 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.
HotPatching Not applicable
Removal Information For DirectShow WMA Voice Codec:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB969878_WM9L$\Spuninst folder

For Windows Media Audio Voice Decoder:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954155_WM9$\Spuninst folder

For Audio Compression Manager:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB975025_WM8$\Spuninst folder
File Information For DirectShow WMA Voice Codec:
See Microsoft Knowledge Base Article 969878

For Windows Media Audio Voice Decoder:
See Microsoft Knowledge Base Article 954155

For Audio Compression Manager:
See Microsoft Knowledge Base Article 975025
Registry Key Verification For DirectShow WMA Voice Codec when installed on Microsoft Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\KB969878_WM9
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB969878_WM9\Filelist

For Windows Media Audio Voice Decoder when installed on Microsoft Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\KB954155_WM9
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB954155_WM9\Filelist

For Audio Compression Manager when installed on Microsoft Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\KB975025_WM8
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB975025_WM8\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
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/extract\[:path\]** Extracts files without starting the Setup program.
**/ER** Enables extended error reporting.
**/verbose** Enables 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For DirectShow WMA Voice Codec when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsMedia9-KB969878-x86-ENU /quiet
For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 2:
WindowsXP-SP2-WindowsMedia-KB954155-x86-ENU /quiet
For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 3:
WindowsXP-WindowsMedia-KB954155-x86-ENU /quiet
For Audio Compression Manager when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB975025-x86-ENU /quiet
For DirectShow WMA Voice Codec when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia9-KB969878-x64-ENU /quiet
For Windows Media Audio Voice Decoder when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB954155-x64-ENU /quiet
For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia10-KB954155-x64-ENU /quiet
For Windows Media Audio Voice Decoder in Windows Media Format SDK 11 when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia11-KB954155-x64-ENU /quiet
For Audio Compression Manager when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB975025-x64-ENU /quiet
Installing without restarting For DirectShow WMA Voice Codec when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsMedia9-KB969878-x86-ENU /norestart
For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 2:
WindowsXP-SP2-WindowsMedia-KB954155-x86-ENU /norestart
For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 3:
WindowsXP-WindowsMedia-KB954155-x86-ENU /norestart
For Audio Compression Manager when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB975025-x86-ENU /norestart
For DirectShow WMA Voice Codec when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia9-KB969878-x64-ENU /norestart
For Windows Media Audio Voice Decoder when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB954155-x64-ENU /norestart
For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia10-KB954155-x64-ENU /norestart
For Windows Media Audio Voice Decoder in Windows Media Format SDK 11 when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia11-KB954155-x64-ENU /norestart
For Audio Compression Manager when installed on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB975025-x64-ENU /norestart
Update log file kb969878.log, kb954155.log, or kb975025.log
Further information See 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.
HotPatching Not applicable
Removal Information For DirectShow WMA Voice Codec:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB969878_WM9L$\Spuninst folder

For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB954155_WM9$\spuninst folder

For Windows Media Audio Voice Decoder when installed on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB954155$\spuninst folder

For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB954155_WM10Lx64$\spuninst folder

For Windows Media Audio Voice Decoder in Windows Media Format SDK 11 when installed on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NtUninstallKB954155_WM11x64$\spuninst folder

For Audio Compression Manager:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB975025$\Spuninst folder
File Information For DirectShow WMA Voice Codec:
See Microsoft Knowledge Base Article 969878

For Windows Media Audio Voice Decoder:
See Microsoft Knowledge Base Article 954155

For Audio Compression Manager:
See Microsoft Knowledge Base Article 975025
Registry Key Verification For DirectShow WMA Voice Codec when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 9 Series\SP0\KB969878_WM9L\Filelist

For DirectShow WMA Voice Codec when installed on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 9 Series\SP0\KB969878_WM9L\Filelist
For Windows Media Audio Voice Decoder when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\KB954155_WM9
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB954155_WM9\Filelist

For Windows Media Audio Voice Decoder when installed on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB954155\Filelist

For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\KB954155_WM10Lx64
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\SP0\KB954155_WM10Lx64\Filelist

For Windows Media Audio Voice Decoder in Windows Media Format SDK 11 when installed on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 11 SDK\KB954155_WM11x64
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 11 SDK\SP0\KB954155_WM11x64\Filelist
For Audio Compression Manager when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB975025

For Audio Compression Manager when installed on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB975025

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
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/integrate:path** Integrates 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.
**/ER** Enables extended error reporting.
**/verbose** Enables 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For DirectShow WMA Voice Codec when installed on all supported 32-bit editions of Windows Server 2003:
WindowsMedia9-KB969878-x86-ENU /quiet
For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB954155-x86-ENU /quiet
For Audio Compression Manager when installed on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB975025-x86-ENU /quiet
For DirectShow WMA Voice Codec when installed on all supported x64-based editions of Windows Server 2003:
WindowsMedia9-KB969878-x64-ENU /quiet
For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB954155-x64-ENU /quiet
For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on all supported x64-based editions of Windows Server 2003:
WindowsMedia10-KB954155-x64-ENU /quiet
For Audio Compression Manager when installed on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB975025-x64-ENU /quiet
Installing without restarting For DirectShow WMA Voice Codec when installed on all supported 32-bit editions of Windows Server 2003:
WindowsMedia9-KB969878-x86-ENU /norestart
For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB954155-x86-ENU /norestart
For Audio Compression Manager when installed on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB975025-x86-ENU /norestart
For DirectShow WMA Voice Codec when installed on all supported x64-based editions of Windows Server 2003:
WindowsMedia9-KB969878-x64-ENU /norestart
For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB954155-x64-ENU /norestart
For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on all supported x64-based editions of Windows Server 2003:
WindowsMedia10-KB954155-x64-ENU /norestart
For Audio Compression Manager when installed on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB975025-x64-ENU /norestart
Update log file kb969878.log, kb954155.log, or kb975025.log
Further information See 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.
HotPatching This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information For DirectShow WMA Voice Codec:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB969878_WM9L$\Spuninst folder

For Windows Media Audio Voice Decoder:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB954155$\Spuninst folder

For Audio Compression Manager:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB975025$\Spuninst folder
File Information For DirectShow WMA Voice Codec:
See Microsoft Knowledge Base Article 969878

For Windows Media Audio Voice Decoder:
See Microsoft Knowledge Base Article 954155

For Audio Compression Manager:
See Microsoft Knowledge Base Article 975025
Registry Key Verification For DirectShow WMA Voice Codec:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 9 Series\KB969878_WM9L
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 9 Series\SP0\KB969878_WM9L\Filelist

For Windows Media Audio Voice Decoder:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB954155\Filelist

For Windows Media Audio Voice Decoder in Windows Media Format SDK 9.5 x64 Edition when installed on all supported x64-based editions of Windows Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\KB954155_WM10Lx64
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK\SP0\KB954155_WM10Lx64\Filelist

For Audio Compression Manager:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB975025\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
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/integrate:path** Integrates 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.
**/ER** Enables extended error reporting.
**/verbose** Enables 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](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended 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.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts 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.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows 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 Vista (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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Vista:
Windows6.0-KB954155-x86 /quiet

For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Vista:
Windows6.0-KB954155-x64 /quiet
Installing without restarting For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Vista:
Windows6.0-KB954155-x86 /quiet /norestart

For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Vista:
Windows6.0-KB954155-x64 /quiet /norestart
Further information See 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.
HotPatching Not applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 954155
Registry Key Verification Note A registry key does not exist to validate the presence of this 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. For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

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 enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB954155-x86 /quiet

For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB954155-x64 /quiet
Installing without restarting For Windows Media Audio Voice Decoder when installed on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB954155-x86 /quiet /norestart

For Windows Media Audio Voice Decoder when installed on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB954155-x64 /quiet /norestart
Further information See 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.
HotPatching Not applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 954155
Registry Key Verification Note A registry key does not exist to validate the presence of this 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. For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches

| Switch | Description |
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. | Table: Supported Security Update Installation Switches

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

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 enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Ivan Fratric of Zero Day Initiative and Jun Xie of McAfee Avert Labs for reporting the Windows Media Runtime Voice Sample Rate Vulnerability (CVE-2009-0555)
  • Vinay Anantharaman of Adobe Systems, Inc. for reporting the Windows Media Runtime Heap Corruption Vulnerability (CVE-2009-2525)

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 (October 13, 2009): Bulletin published.
  • V1.1 (October 14, 2009): Clarified the entry, "I have Windows Media Player installed on my system. Why am I not being offered some of the updates?" in the FAQ section. Also corrected the FAQ for CVE-2009-0555 to indicate that Microsoft is aware of limited attacks attempting to exploit the vulnerability.
  • V2.0 (November 10, 2009): Bulletin revised to communicate the rerelease of the update for Audio Compression Manager on Microsoft Windows 2000 Service Pack 4 to fix a detection issue. This is a detection change only; there were no changes to the binaries. Customers who have successfully updated their systems do not need to reinstall this update. Also corrected the registry key verification for DirectShow WMA Voice Codec on Windows Server 2003.

Built at 2014-04-18T13:49:36Z-07:00