Microsoft Security Bulletin MS07-068 - Critical
Vulnerability in Windows Media File Format Could Allow Remote Code Execution (941569 and 944275)
Published: | Updated:
Version: 2.3
General Information
Executive Summary
This critical security update resolves a privately reported vulnerability in Windows Media File Format. This vulnerability could allow remote code execution if a user viewed a specially crafted file in Windows Media Format Runtime. 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 is a critical security update for supported editions of Windows Media Format Runtime 7.1, 9, 9.5, 11 and for Windows Media Services 9.1. For more information, see the subsection, Affected and Non-Affected Software, in this section.
For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately.
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 |
|---|---|---|---|---|
| Windows Media Format Runtime 7.1 | ||||
| Microsoft Windows 2000 Service Pack 4 | Windows Media Format Runtime 7.1 (KB941569) | Remote Code Execution | Critical | MS06-078 |
| Windows Media Format Runtime 9 | ||||
| Windows 2000 Service Pack 4 | Windows Media Format Runtime 9 (KB941569) | Remote Code Execution | Critical | MS06-078 |
| Windows XP Service Pack 2 | Windows Media Format Runtime 9 (KB941569) | Remote Code Execution | Critical | MS06-078 |
| Windows Media Format Runtime 9.5 | ||||
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Windows Media Format Runtime 9.5 (KB941569) | Remote Code Execution | Critical | See FAQ Related to This Security Update |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 (KB941569) | Remote Code Execution | Critical | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Windows Media Format Runtime 9.5 (KB941569) | Remote Code Execution | Critical | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 (KB941569) | Remote Code Execution | Critical | None |
| Windows Media Format Runtime 9.5 x64 Edition | ||||
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 x64 Edition (KB941569) | Remote Code Execution | Critical | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Format Runtime 9.5 x64 Edition (KB941569) | Remote Code Execution | Critical | None |
| Windows Media Format Runtime 11 | ||||
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Windows Media Format Runtime 11 (KB941569) | Remote Code Execution | Critical | See FAQ Related to This Security Update |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Windows Media Format Runtime 11 (KB941569) | Remote Code Execution | Critical | None |
| Windows Vista | Windows Media Format Runtime 11 (KB941569) | Remote Code Execution | Critical | None |
| Windows Vista x64 Edition | Windows Media Format Runtime 11 (KB941569) | Remote Code Execution | Critical | None |
| Windows Media Services 9.1 | ||||
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Windows Media Services 9.1 (KB944275) | Remote Code Execution | Critical | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Windows Media Services 9.1 x64 Edition (KB944275) | Remote Code Execution | Critical | None |
Non-Affected Software
| Software |
|---|
| Windows Media Player 6.4 when installed on Microsoft Windows 2000 |
| Windows Media Player 6.4 when installed on Windows XP |
| Windows Media Player 6.4 when installed on Windows Server 2003 |
| Windows Media Services 4.1 when installed on Microsoft Windows 2000 |
| Windows Media Format Runtime 9 when installed on Windows XP Service Pack 3 |
| Microsoft Windows 2003 For Itanium-Based Systems and Windows Server 2003 with SP1 for Itanium-based Systems |
Frequently Asked Questions (FAQ) Related to This Security Update
Why did Microsoft reissue this bulletin on August 20, 2008?
This bulletin has been reissued to move Windows Media Format Runtime 9 when installed on Windows XP Service Pack 3 to the Non-Affected Software table.
Why did Microsoft reissue this bulletin on June 10, 2008?
This bulletin has been reissued to add Windows Media Format Runtime 9, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 as affected components for Windows XP Service Pack 3. This is a detection change only to offer and install the package on Windows XP Service Pack 3 systems. There were no changes to the binaries. Customers with Windows XP who have already installed the security update will not need to reinstall the update after applying Windows XP Service Pack 3.
What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 941569 and Microsoft Knowledge Base Article 944275 document the currently known issues that customers may experience when they install this security update. The articles also document recommended solutions for these issues.
On Windows XP Service Pack 2 and Windows XP Service Pack 3, does this bulletin replace all updates offered by MS06-078?
For Windows Media Format Runtime 9.5 and Windows Media Format Runtime 11 on Windows XP Service Pack 2 and Windows XP Service Pack 3, the update offered by Microsoft Knowledge Base Article 941569 will not supersede MS06-078. For Windows Media Format Runtime 9 on Windows XP Service Pack 2, the update offered by Microsoft Knowledge Base Article 941569 will partially supersede MS06-078, replacing the Windows Media Format Runtime 9 update addressed by Microsoft Knowledge Base Article 923689. The update for Media Player 6.4 addressed in MS06-078 (925398) is not superseded and will still need to be deployed for Windows XP Service Pack 2.
When deploying this update using WSUS, why am I offered two update bundles with identical titles and descriptions?
Customers using Windows Server Update Services (WSUS) will see two update bundles which have identical titles and descriptions for Windows XP Service Pack 2 and Windows XP Service Pack 3. This issue results from separation of detection metadata to detect different versions of Windows Media Format Runtime on Windows XP Service Pack 2 and Windows XP Service Pack 3. The solution is to deploy both update bundles for Windows XP Service Pack 2 and Windows XP Service Pack 3. For customers installing this update through Windows Update the Microsoft detections and deployment tools will install the correct updates so all files are replaced as superseded.
For Windows XP Professional x64 Edition, do I need to install both Windows Media Format Runtime updates: the Windows Media Format Runtime 9.5 for Windows XP Professional x64 Edition and the Windows Media Format Runtime 9.5 x64 Edition for Windows XP Professional x64 Edition?
Yes, there may be situations where you need to install both updates. If you installed Windows Media Format Runtime x64 Edition, you have to install both the Windows Media Format Runtime 9.5 for Windows XP Professional x64 Edition and the Windows Media Format Runtime 9.5 x64 Edition for Windows XP Professional x64 Edition.
For Windows Server 2003 x64 Edition, do I need to install both Windows Media Format Runtime updates: the Windows Media Format Runtime 9.5 for Windows Server 2003 x64 Edition and the Windows Media Format Runtime 9.5 x64 Edition for Windows Server 2003 x64 Edition?
Yes, there may be situations where you need to install both updates. If you installed Windows Media Format Runtime x64 Edition, you have to install both the Windows Media Format Runtime 9.5 for Windows Server 2003 x64 Edition and the Windows Media Format Runtime 9.5 x64 Edition for Windows Server 2003 x64 Edition.
Why is Windows Server 2003 for Itanium-based Systems not listed in the affected or non-affected software sections?
Windows Media Format Runtime is not an installable component on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems. Windows Media Services did not ship as an optional component on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems.
I am using an older release of the software discussed in this security bulletin. What should I do?
This software has 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 the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software releases, visit the Microsoft Product Support Services Web site.
Customers who require custom support for older software 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 the Microsoft Worldwide Information Web site, 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.
I’ve installed the Window Media Format (KB941569) security update, what version of wmasf.dll should I have installed?
Microsoft has provided detection and deployment guidance for these security updates. 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. To manually verify what file version of wmasf.dll should have been installed please refer to the following tables.
For Windows Media Format Runtime 7.1 on Microsoft Windows 2000 Service Pack 4:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 7.10.0.3081 | 31-Oct-2007 | 10:17 | 245,760 |
| wmvcore.dll | 7.10.0.3081 | 31-Oct-2007 | 10:18 | 1,134,592 |
For Windows Media Format Runtime 9 on Microsoft Windows 2000 Service Pack 4, you may have either version 9.0.0.3355 or 9.0.0.3267 depending on your configuration:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 9.0.0.3355 | 31-Oct-2007 | 10:17 | 222,720 |
| wmvcore.dll | 9.0.0.3355 | 31-Oct-2007 | 10:17 | 2,064,384 |
| wmasf.dll | 9.0.0.3267 | 31-Oct-2007 | 10:17 | 230,912 |
| wmvcore.dll | 9.0.0.3267 | 31-Oct-2007 | 10:17 | 2,109,440 |
Windows Media Format Runtime 9 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 9.0.0.3355 | 28-Oct-2007 | 24:38 | 222,720 | SP1GDR |
| wmvcore.dll | 9.0.0.3355 | 28-Oct-2007 | 24:39 | 2,064,384 | SP1QFE |
| wmasf.dll | 9.0.0.3267 | 28-Oct-2007 | 24:39 | 230,912 | SP1GDR |
| wmvcore.dll | 9.0.0.3267 | 28-Oct-2007 | 24:37 | 2,109,440 | SP1QFE |
Windows Media Format Runtime 9.5 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.4359 | 28-Oct-2007 | 24:39 | 228,864 | SP1GDR |
| wmasf.dll | 10.0.0.4060 | 28-Oct-2007 | 24:40 | 227,328 | SP1QFE |
For Windows Media Format Runtime 9.5 when installed on all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.3710 | 23-Oct-2007 | 21:58 | 226, 816 | SP1GDR |
| wmasf.dll | 10.0.0.3710 | 23-Oct-2007 | 22:16 | 226,816 | SP1QFE |
| wmasf.dll | 10.0.0.4000 | 23-Oct-2007 | 22:32 | 228,864 | SP2GDR |
| wmasf.dll | 10.0.0.4000 | 23-Oct-2007 | 22:53 | 228,864 | SP2QFE |
For Windows Media Format Runtime 9.5 x64 Edition when installed on all supported x64-based editions of Windows XP or Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU |
|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.3811 | 29-Oct-2007 | 12:55 | 455,168 | X64 |
For Windows Media Format Runtime 9.5 when installed on all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.3710 | 24-Oct-2007 | 13:07 | 226,816 | x86 | SP1GDR\WOW |
| wmasf.dll | 10.0.0.3710 | 24-Oct-2007 | 13:07 | 226,816 | x86 | SP1QFE\WOW |
| wmasf.dll | 10.0.0.4000 | 24-Oct-2007 | 13:17 | 228,864 | x86 | SP2GDR\WOW |
| wmasf.dll | 10.0.0.4000 | 24-Oct-2007 | 13:05 | 228,864 | x86 | SP2QFE\WOW |
Windows Media Format Runtime 11 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 11.0.5721.5238 | 28-Oct-2007 | 24:40 | 222,720 |
Windows Media Format Runtime 11 when installed on all supported x64-based editions of Windows XP:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 11.0.5721.5238 | 29-Oct-2007 | 10:31 | 222,720 | x86 | SP1QFE\WOW |
For Windows Media Format Runtime 11 on all supported 32-bit editions of Windows Vista:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | Windows6.0-KB941569-x86\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_a57e3226437ddd6f |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | Windows6.0-KB941569-x86\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.20708_none_a66151155c57e6dd |
For Windows Media Format Runtime 11 on all supported x64-based editions of Windows Vista:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 24:18 | 301,056 | x64 | Windows6.0-KB941569-x64\amd64_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_019ccda9fbdb4ea5 |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 04:05 | 301,056 | x64 | Windows6.0-KB941569-x64\amd64_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.20708_none_027fec9914b55813 |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | x86 | Windows6.0-KB941569-x64\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_a57e3226437ddd6f |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | x86 | Windows6.0-KB941569-x64\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000 |
I’ve installed the Windows Media Services 9.1(KB944275) security update, what version of wmsserver.dll should I have installed?
Microsoft has provided detection and deployment guidance for these security updates. 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. To manually verify what file version of wmsserver.dll should have been installed please refer to the following tables.
Note Windows Media Services 9.1, which includes wmsserver.dll, is an optional operating system component on all supported 32-bit editions of Windows Server 2003, and x64-based editions of Windows Server 2003.
Note Windows Media Services 9.1, which includes wmsserver.dll, is not installable on any supported edition of Windows XP.
For Windows Media Services 9.1 when installed on all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 05:16 | 3,098,624 | SP1GDR |
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 04:59 | 3,167,232 | SP1QFE |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 05:04 | 3,167,744 | SP2GDR |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 05:13 | 3,167,744 | SP2QFE |
For Windows Media Services 9.1 when installed all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 19:21 | 5,814,272 | x86 | SP1GDR |
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 19:21 | 5,821,952 | x86 | SP1QFE |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 19:27 | 5,821,952 | x86 | SP2GDR |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 19:20 | 5,821,952 | x86 | SP2QFE |
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Windows Media Format Remote Code Execution Vulnerability Parsing ASF - CVE-2007-0064 | Aggregate Severity Rating |
|---|---|---|
| Windows Media Format Runtime 7.1 | Critical Remote Code Execution | Critical |
| Windows Media Format Runtime 9 | Critical Remote Code Execution | Critical |
| Windows Media Format Runtime 9.5 | Critical Remote Code Execution | Critical |
| Windows Media Format Runtime 11 | Critical Remote Code Execution | Critical |
| Windows Media Format Runtime 9.5 x64 Edition | Critical Remote Code Execution | Critical |
| Windows Media Services 9.1 | Critical Remote Code Execution | Critical |
Windows Media Format Remote Code Execution Vulnerability Parsing ASF - CVE-2007-0064
A remote code execution vulnerability exists in Windows Media Format Runtime due to the way it handles Advanced Systems Format (ASF) files. In client applications, such as Windows Media Player, an attacker could exploit the vulnerability by constructing specially crafted Windows Media Format Runtime content that could potentially allow remote code execution if a user visits a specially crafted Web site or opens an e-mail message with specially crafted content. In server applications, such as Windows Media Services, an attacker could exploit the vulnerability by constructing specially crafted Windows Media Format Runtime content that could potentially allow remote code execution if the server processes the specially crafted content. In client and server applications, 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-2007-0064.
Mitigating Factors for Windows Media Format Remote Code Execution Vulnerability Parsing ASF – CVE-2007-0064
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, which could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- Mitigating Factors for Client Application:
- 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 convince 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 Media Player 6.4 when installed on Windows 2000, Windows XP, or Windows Server 2003 is not affected.
- Mitigating Factors for Server Application:
- An attacker who successfully exploited this vulnerability could gain the same privileges as the network service account.
- Windows Media Services 9.1, which includes wmsserver.dll, is an optional operating system component on all supported 32-bit editions of Windows Server 2003, and x64-based editions of Windows Server 2003.
Workarounds for Windows Media Format Remote Code Execution Vulnerability Parsing ASF – CVE-2007-0064
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:
The core workaround for these vulnerabilities is to deny access to the vulnerable DLLs on each affected operating system.
- For client applications deny access to WMASF.DLL
From an administrative command prompt in Windows XP and Windows Server 2003 run the following command:
Echo y| cacls exe %WINDIR%\SYSTEM32\WMASF.DLL /E /P everyone:NFrom an elevated command prompt in Windows Vista run the following commands:
Takeown.exe /f %WINDIR%\SYSTEM32\WMASF.DLL
Icacls.exe %WINDIR%\SYSTEM32\WMASF.DLL /save %TEMP%\WMASF_ACL.TXT
Icacls.exe %WINDIR%\SYSTEM32\WMASF.DLL /deny everyone:(F)Impact of Workaround: Users will be unable to play Advanced Systems Format (ASF) files.
- For server applications, Microsoft has not identified any workarounds for this vulnerability.
FAQ for Windows Media Format Remote Code Execution Vulnerability Parsing ASF - CVE-2007-0064
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Windows Media Format Runtime due to the way it handles Advanced Systems Format (ASF) files. In client applications, such as Windows Media Player, an attacker could exploit the vulnerability by constructing specially crafted Windows Media Format Runtime content that could potentially allow remote code execution if a user visits a specially crafted Web site or opens an e-mail message with specially crafted content. In server applications, such as Windows Media Services, an attacker could exploit the vulnerability by constructing specially crafted Windows Media Format Runtime content that could potentially allow remote code execution if the server processes the specially crafted content. In client and server applications, an attacker who successfully exploited this vulnerability could take complete control of an affected system.
What causes the vulnerability?
Incorrect parsing of Advanced Systems Format (ASF) files within the Windows Media Format Runtime.
What is Windows Media Format Runtime?
The Microsoft Windows Media Format Runtime provides information and tools for applications that use Windows Media content. For more information, see the product documentation.
What is Windows Media Services 9.1?
The Windows Media Services 9.1, which includes wmsserver.dll, is an optional operating system component on all supported 32-bit editions of Windows Server 2003, and x64-based editions of Windows Server 2003. This server application runs as a low privileged networking service account for processing media files. For more information, see the product documentation.
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 contains 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 extensions ASF, WMV, or WMA.
What might an attacker use the vulnerability to do?
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 are less impacted than users who operate with administrative user rights.
How could an attacker exploit the vulnerability?
In a client Web-based attack scenario, an attacker could host a Web site designed to exploit this vulnerability through Windows Media Player. In no case, however, would an attacker have a way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. In server applications an attacker could exploit the vulnerability by constructing specially crafted Windows Media Format Runtime content that could potentially allow remote code execution if the server processes the specially crafted content.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and opens the specially crafted ASF file in any Windows Media Format Runtime-based application for any malicious action to occur. Therefore, any systems where Windows Media Format Runtime or Windows Media Server 9.1 s used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update removes the vulnerability by modifying the way that Windows Media Format Runtime parses Advanced Systems Format (ASF) files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
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 computers 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, Windows Update, and Office 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.
Detection and Deployment Guidance
Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
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.0.1 |
|---|---|
| Windows Media Format Runtime 7.1 | Yes |
| Windows Media Format Runtime 9 | Yes |
| Windows Media Format Runtime 9.5 | Yes |
| Windows Media Format Runtime 11 | Yes |
For more information about MBSA 2.0.1, see MBSA 2.0 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 to Windows 2000 and later operating systems. 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.
| Software | SMS 2.0 | SMS 2003 |
|---|---|---|
| Windows Media Format Runtime 7.1 | Yes | Yes |
| Windows Media Format Runtime 9 | Yes | Yes |
| Windows Media Format Runtime 9.5 | Yes | Yes |
| Windows Media Format Runtime 11 | No | Yes |
For SMS 2.0, the SMS SUS Feature Pack, 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.
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.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 Service Pack 4
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 Windows Media Format Runtime 7.1 or 9: Windows2000-KB941569-NEC98-JPN.exe /quiet Windows2000-KB941569-x86-ENU.exe /quiet |
| Installing without restarting | For Windows Media Format Runtime 7.1 or 9: Windows2000-KB941569-NEC98-JPN.exe /norestart Windows2000-KB941569-x86-ENU.exe /norestart |
| Update log file | KB941569.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hotpatching | Not applicable. |
| Removal Information | To remove this security update, use the Add or Remove Programs tool in Control Panel. System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB941569$\Spuninst folder. |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | For Windows Media Format Runtime 7.1 or 9: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows 2000\SP1\KB941569\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For Windows Media Format Runtime 7.1 on Microsoft Windows 2000 Service Pack 4:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 7.10.0.3081 | 31-Oct-2007 | 10:17 | 245,760 |
| wmvcore.dll | 7.10.0.3081 | 31-Oct-2007 | 10:18 | 1,134,592 |
For Windows Media Format Runtime 9 on Microsoft Windows 2000 Service Pack 4, you may have either version 9.0.0.3355 or 9.0.0.3267 depending on your configuration:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 9.0.0.3355 | 31-Oct-2007 | 10:17 | 222,720 |
| wmvcore.dll | 9.0.0.3355 | 31-Oct-2007 | 10:17 | 2,064,384 |
| wmasf.dll | 9.0.0.3267 | 31-Oct-2007 | 10:17 | 230,912 |
| wmvcore.dll | 9.0.0.3267 | 31-Oct-2007 | 10:17 | 2,109,440 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 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.
| 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 | Display 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 |
| /forceapsclose | 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.
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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 may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | For Windows Media Format Runtime 9, 9.5 or 11 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsXP-KB941569-x86-ENU.exe /quiet For Windows Media Format Runtime 9.5 when installed on all supported x64-based editions of Windows XP: WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe /quiet For Windows Media Format Runtime 11 when installed on all supported x64-based editions of Windows XP: WindowsMedia11-KB941569-x64-ENU.exe /quiet WindowsMedia10-KB941569-x64-ENU.exe /quiet |
| Installing without restarting | For Windows Media Format Runtime 9, 9.5 or 11 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsXP-KB941569-x86-ENU.exe /norestart For Windows Media Format Runtime 9.5 when installed on all supported x64-based editions of Windows XP: WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe /norestart For Windows Media Format Runtime 11 when installed on all supported x64-based editions of Windows XP: WindowsMedia11-KB941569-x64-ENU.exe /norestart For Windows Media Format Runtime 9.5 x64 Edition when installed on all supported x64-based editions of Windows XP: WindowsMedia10-KB941569-x64-ENU.exe /norestart |
| Update log file | KB941569.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hotpatching | Not applicable. |
| Removal Information | To remove this security update, use the Add or Remove Programs tool in Control Panel. System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB941569$\Spuninst folder. |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | For Windows Media Format Runtime 9, 9.5 or 11 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB941569\Filelist For Windows Media Format Runtime 9.5 when installed on all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB941569\Filelist For Windows Media Format Runtime 11 when installed on all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Format 11 SDK\SP2\KB941569_WM11\Filelist For Windows Media Format Runtime 9.5 x64 Edition when installed on all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Format 9.5 SDK x64 Edition\SP2\KB941569_FSDK64\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Media Format Runtime 9 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 9.0.0.3355 | 28-Oct-2007 | 24:38 | 222,720 | SP1GDR |
| wmvcore.dll | 9.0.0.3355 | 28-Oct-2007 | 24:39 | 2,064,384 | SP1QFE |
| wmasf.dll | 9.0.0.3267 | 28-Oct-2007 | 24:39 | 230,912 | SP1GDR |
| wmvcore.dll | 9.0.0.3267 | 28-Oct-2007 | 24:37 | 2,109,440 | SP1QFE |
Windows Media Format Runtime 9.5 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.4359 | 28-Oct-2007 | 24:39 | 228,864 | SP1GDR |
| wmasf.dll | 10.0.0.4060 | 28-Oct-2007 | 24:40 | 227,328 | SP1QFE |
Windows Media Format Runtime 11 when installed on all supported 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 11.0.5721.5238 | 28-Oct-2007 | 24:40 | 222,720 |
Windows Media Format Runtime 11 when installed on all supported x64-based editions of Windows XP:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 11.0.5721.5238 | 29-Oct-2007 | 10:31 | 222,720 | X86 | SP1QFE\WOW |
Windows Media Format Runtime 9.5 Series x64 Edition when installed on all supported x64-based editions of Windows XP:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 10.0.0.3811 | 29-Oct-2007 | 24:55 | 455,168 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 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.
| 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 | Display 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.
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Note Windows Media Services 9.1, which includes wmsserver.dll, is not installable on any supported edition of Windows XP.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | For Windows Media Format Runtime 9.5: WindowsServer2003-KB941569-x86-ENU.exe /quiet WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe /quiet For Windows Media Format Runtime 9.5 x64 Edition when installed on all supported x64-based editions of Windows Server 2003: WindowsMedia10-KB941569-x64-ENU.exe /quiet For 32-bit editions of Windows Media Services 9.1: WindowsServer2003-KB944275-x86-ENU.exe /quiet For x64-based editions of Windows Media Services 9.1: WindowsServer2003.WindowsXP-KB944275-x64-ENU.exe /quiet |
| Installing without restarting | For Windows Media Format Runtime 9.5: WindowsServer2003-KB941569-x86-ENU.exe /norestart WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe /norestart For Windows Media Format Runtime 9.5 x64 Edition when installed on all supported x64-based editions of Windows Server 2003: WindowsMedia10-KB941569-x64-ENU.exe /norestart For 32-bit editions of Windows Media Services 9.1: WindowsServer2003-KB944275-x86-ENU.exe /norestart For x64-based editions of Windows Media Services 9.1: WindowsServer2003.WindowsXP-KB944275-x64-ENU.exe /norestart |
| Update log file | KB941569.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| Hotpatching | This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341. |
| Removal Information | To remove this security update, use the Add or Remove Programs tool in Control Panel. System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB941569$\Spuninst folder and the %Windir%\$NTUninstallKB944275$\Spuninst folder. |
| File Information | See the next subsection, File Information, for the full file manifest |
| Registry Key Verification | For Windows Media Format Runtime 9.5 SP1 and Windows Media Format Runtime 9.5 SP2: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB941569\Filelist For Windows Media Format Runtime 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 x64 Edition\SP2\KB941569_FSDK64\Filelist |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For Windows Media Format Runtime 9.5 when installed on all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.3710 | 23-Oct-2007 | 21:58 | 226, 816 | SP1GDR |
| wmasf.dll | 10.0.0.3710 | 23-Oct-2007 | 22:16 | 226,816 | SP1QFE |
| wmasf.dll | 10.0.0.4000 | 23-Oct-2007 | 22:32 | 228,864 | SP2GDR |
| wmasf.dll | 10.0.0.4000 | 23-Oct-2007 | 22:53 | 228,864 | SP2QFE |
For Windows Media Format Runtime 9.5 when installed on all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 10.0.0.3710 | 24-Oct-2007 | 13:07 | 226,816 | x86 | SP1GDR\WOW |
| wmasf.dll | 10.0.0.3710 | 24-Oct-2007 | 13:07 | 226,816 | x86 | SP1QFE\WOW |
| wmasf.dll | 10.0.0.4000 | 24-Oct-2007 | 13:17 | 228,864 | x86 | SP2GDR\WOW |
| wmasf.dll | 10.0.0.4000 | 24-Oct-2007 | 13:05 | 228,864 | x86 | SP2QFE\WOW |
Windows Media Format Runtime 9.5 Series x64 Edition when installed on all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| wmasf.dll | 10.0.0.3811 | 29-Oct-2007 | 24:55 | 455,168 |
For Windows Media Services 9.1 when installed on all supported 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 05:16 | 3,098,624 | SP1GDR |
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 04:59 | 3,167,232 | SP1QFE |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 05:04 | 3,167,744 | SP2GDR |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 05:13 | 3,167,744 | SP2QFE |
For Windows Media Services 9.1 when installed all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 19:21 | 5,814,272 | x86 | SP1GDR |
| wmsserver.dll | 9.1.1.3844 | 13-Nov-2007 | 19:21 | 5,821,952 | x86 | SP1QFE |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 19:27 | 5,821,952 | x86 | SP2GDR |
| wmsserver.dll | 9.1.1.3862 | 13-Nov-2007 | 19:20 | 5,821,952 | x86 | SP2QFE |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 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.
| 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 | Display 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.
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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 may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | Windows6.0-KB941569-x86.exe /quiet Windows6.0-KB941569-x64.exe /quiet |
| Installing without restarting | Windows6.0-KB941569-x86.exe /norestart Windows6.0-KB941569-x64.exe /norestart |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. |
| 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 the next subsection, File Information, for the full file manifest |
| Registry Key Verification | No registry key exists for Windows Media Format Runtime 11 on Windows Vista. Use Windows Management Instrumentation to detect the presence of this update. |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For Windows Media Format Runtime 11 on all supported 32-bit editions of Windows Vista:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | Windows6.0-KB941569-x86\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_a57e3226437ddd6f |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | Windows6.0-KB941569-x86\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.20708_none_a66151155c57e6dd |
For Windows Media Format Runtime 11 on all supported x64 editions of Windows Vista:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 24:18 | 301,056 | x64 | Windows6.0-KB941569-x64\amd64_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_019ccda9fbdb4ea5 |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 04:05 | 301,056 | x64 | Windows6.0-KB941569-x64\amd64_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.20708_none_027fec9914b55813 |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | x86 | Windows6.0-KB941569-x64\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000.16585_none_a57e3226437ddd6f |
| wmasf.dll | 11.0.6000.6345 | 25-Oct-2007 | 03:15 | 223,232 | x86 | Windows6.0-KB941569-x64\x86_microsoft-windows-mediaplayer-wmasf_31bf3856ad364e35_6.0.6000 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.
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 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.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /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 |
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.
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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:
- Ryan Smith, IBM Internet Security Systems X-Force Researcher, of ISS X-Force for reporting the Windows Media Format Code Execution Vulnerability – (CVE-2007-0064).
- Alex Wheeler, IBM Internet Security Systems X-Force Researcher, of ISS X-Force for reporting the Windows Media Format Code Execution Vulnerability – (CVE-2007-0064).
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- 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 (December 11, 2007): Bulletin published.
- V1.1 (December 19, 2007): Bulletin updated to reflect a change to the Removal Information text in the Reference Table portion of the Security Update Information section for Windows Vista.
- V1.2 (January 23, 2008): Bulletin updated to add an FAQ regarding installing the updates for Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition.
- V1.3 (February 6, 2008): Bulletin updated to add correct link for Windows Media Format Runtime 9.5 x64 Edition in the Affected Software table. Also corrected the FAQ regarding installing the updates for Windows Media Format Runtime 9.5 on Windows XP Professional x64 Edition and added a similar FAQ for Windows Server 2003 x64 Edition.
- V2.0 (June 10, 2008): Bulletin updated to add Windows Media Format Runtime 9, Windows Media Format Runtime 9.5, and Windows Media Format Runtime 11 as affected components for Windows XP Service Pack 3. This is a detection change only. There were no changes to the binaries.
- V2.1 (June 18, 2008): Bulletin updated to clarify the Update FAQ entry on MS06-078 supersedence, and to add an Update FAQ entry describing a Windows XP installation issue when installing via Windows Server Update Services (WSUS).
- V2.2 (August 20, 2008): Bulletin updated to change Windows Media Format Runtime 9 to a non-affected component when installed on Windows XP Service Pack 3.
- V2.3 (November 25, 2008): Bulletin updated to correct the filename of wwmasf.dll to wmasf.dll in the file information for Windows Media Format 9.5 Runtime for Windows Server 2003 x64 Edition.