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

Microsoft Security Bulletin MS07-047 - Important

Vulnerabilities in Windows Media Player Could Allow Remote Code Execution (936782)

Published: August 14, 2007 | Updated: September 10, 2008

Version: 2.1

General Information

Executive Summary

This important security update resolves two privately reported vulnerabilities. These vulnerabilities could allow code execution if a user viewed a specially crafted file in Windows Media Player. 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 an important security update for supported versions of Windows Media Player 7.1, 9, 10, and 11. For more information, see the subsection, Affected and Non-Affected Software, in this section.

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. Microsoft recommends that customers apply the update.

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

Affected and Non-Affected Software

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

Affected Software

Operating SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by This Update
Windows 2000 Service Pack 4Windows Media Player 7.1Remote Code ExecutionImportantMS06-024
Windows 2000 Service Pack 4Windows Media Player 9Remote Code ExecutionImportantMS06-024
Windows XP Service Pack 2Windows Media Player 9Remote Code ExecutionImportantMS06-024
Windows XP Service Pack 2Windows Media Player 10Remote Code ExecutionImportantMS06-024
Windows XP Service Pack 3Windows Media Player 10Remote Code ExecutionImportantNone
Windows XP Professional X64 EditionWindows Media Player 10Remote Code ExecutionImportantMS06-024
Windows XP Professional X64 Edition Service Pack 2Windows Media Player 10Remote Code ExecutionImportantNone
Windows Server 2003 Service Pack 1Windows Media Player 10Remote Code ExecutionImportantMS06-024
Windows Server 2003 Service Pack 2Windows Media Player 10Remote Code ExecutionImportantNone
Windows Server 2003 x64 EditionWindows Media Player 10Remote Code ExecutionImportantMS06-024
Windows Server 2003 x64 Edition Service Pack 2Windows Media Player 10Remote Code ExecutionImportantNone
Windows XP Service Pack 2Windows Media Player 11Remote Code ExecutionImportantMS06-024
Windows XP Service Pack 3Windows Media Player 11Remote Code ExecutionImportantNone
Windows XP Professional X64 EditionWindows Media Player 11Remote Code ExecutionImportantMS06-024
Windows XP Professional X64 Edition Service Pack 2Windows Media Player 11Remote Code ExecutionImportantNone
Windows VistaWindows Media Player 11Remote Code ExecutionImportantNone
Windows Vista x64 EditionWindows Media Player 11Remote Code ExecutionImportantNone

Why was this security bulletin revised on September 10, 2008? 
Microsoft revised this security bulletin to remove Windows Media Player 9 on Windows XP Service Pack 3 from the Affected Software table. This is a bulletin change only; there were no changes to detection or to the binaries. Customers who have successfully updated their systems do not need to reinstall this update.

Why was this security bulletin revised on August 12, 2008? 
Microsoft revised this security bulletin to add Windows XP Service Pack 3 as affected software upon which Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 run. 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.

What are the known issues that customers may experience when they install this security update? 
Microsoft Knowledge Base Article 936782 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

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

Does this update contain any security-related changes to functionality? 
Yes. Besides the changes that are listed in the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the bulletin section, Vulnerability Information, this update includes defense-in-depth changes to Windows Media Player. For more information about the defense-in-depth, see Microsoft Knowledge Base Article 940893.

Vulnerability Information

Affected SoftwareWindows Media Player Code Execution Vulnerability Parsing Skins – CVE-2007-3037Windows Media Player Code Execution Vulnerability Decompressing Skins - CVE-2007-3035Aggregate Severity Rating
Windows Media Player 7.1Important
Remote Code Execution
Important
Remote Code Execution
Important
Windows Media Player 9Important
Remote Code Execution
Important
Remote Code Execution
Important
Windows Media Player 10Important
Remote Code Execution
Important
Remote Code Execution
Important
Windows Media Player 11Important
Remote Code Execution
Important
Remote Code Execution
Important

A code execution vulnerability exists in Windows Media Player skin parsing. 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-3037.

Mitigating Factors for Windows Media Player Code Execution Vulnerability Parsing Skins – CVE-2007-3037

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:

  • When a user attempts to install a Windows Media Player skin file, the user is prompted with a "Windows Media Download" dialog box prior to the skin being applied.
  • Attempts to exploit the vulnerability using WMZ and WMD files require the user to view or apply the skin after it is downloaded to be vulnerable.

Workarounds for Windows Media Player Code Execution Vulnerability Parsing Skins – CVE-2007-3037

Disassociate the WMZ and WMD file extensions

Disassociation of WMZ and WMD in Windows prevents previewing or opening WMZ and WMD files in Windows Media Player.

  1. Click Start, click Run, type "regedit” (without the quotation marks), and then click OK.
  2. Expand HKEY_CLASSES_ROOT, and click .WMZ, and then right click and select Export. Note: This will create a backup of this registry key in the ‘My Documents’ folder by default.
  3. In the Export Registry File window, type “WMZ file association registry backup.reg” and press Save.

    This will create a backup of this registry key in the “My Documents” folder by default.
  4. Press the Delete key on the keyboard to delete the registry key. Select Yes to confirm the registry key deletion.
  5. Repeat steps 2-5 for the WMDkey.

Impact of Workaround: This workaround prevents users from applying skin files to Windows Media Player by double clicking on them. Users can still apply skin files that are in their default ‘skins’ directory.

Un-register Wmp.dll

  1. Un-registering the Wmp.dll registry key helps protect the affected system from attempts to exploit this vulnerability. To modify the Wmp.dll registry key, follow these steps.
  2. Click Start, click Run, type "regsvr32 -u %windir%\system32\wmp.dll" (without the quotation marks), and then click OK.
  3. When a dialog box appears that confirms that the process has been successful, click OK.
  4. Select the File Types tab.

Impact of Workaround: This workaround disables the Windows Media Player and applications that use the embedded Windows Media ActiveX Control.

FAQ for Windows Media Player Code Execution Vulnerability Parsing Skins – CVE-2007-3037

What is the scope of the vulnerability? 
A code execution vulnerability exists in Windows Media Player parsing skins. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs or view, change, or delete data.

What causes the vulnerability? 
Windows Media Player incorrectly handles header information contained in skin files.

What is a skin file? 
Skins are sets of scripts, art, media, and text files that can be combined to create a new appearance for Windows Media Player. Using skins, you can change not only the way Windows Media Player looks, but how it functions. Windows Media Player skin files are distributed in WMZ and WMD files.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of an affected system. Users whose accounts are configured to have fewer user rights on the guest operating system are less impacted than users who operate with administrative user rights on the guest operating system.

How could an attacker exploit the vulnerability? 
In a Web-based attack scenario, an attacker could host a specially-crafted skin file designed to exploit this vulnerability through Windows Media Player and then convince a user to view the skins file. 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 an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted skin file to the user and by persuading the user to open the file.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user is logged on and opens the malicious skin file in Windows Media Player for any malicious action to occur. Therefore, any systems where Windows Media Player is 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 changing Windows Media Player to correctly handle header information contained in skin 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.

A remote code execution vulnerability exists in 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-2007-3035.

Mitigating Factors for Windows Media Player Code Execution Vulnerability Decompressing Skins - CVE-2007-3035

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:

  • When a user attempts to install a Windows Media Player skin file, the user is prompted with a "Windows Media Download" dialog box prior to the skin being applied.
  • Attempts to exploit the vulnerability using WMZ and WMD files require the user to view or apply the skin after it is downloaded to be vulnerable.

Workarounds for Windows Media Player Code Execution Vulnerability Decompressing Skins - CVE-2007-3035

Disassociate the WMZ and WMD file extensions

Disassociation of WMZ and WMD in Windows prevents previewing or opening WMZ and WMD files in Windows Media Player.

  1. Click Start, click Run, type "regedit” (without the quotation marks), and then click OK.
  2. Expand HKEY_CLASSES_ROOT, and click .WMZ, and then right click and select Export. Note: This will create a backup of this registry key in the ‘My Documents’ folder by default.
  3. In the Export Registry File window, type “WMZ file association registry backup.reg” and press Save.

    This will create a backup of this registry key in the “My Documents” folder by default.
  4. Press the Delete key on the keyboard to delete the registry key. Select Yes to confirm the registry key deletion.
  5. Repeat steps 2-5 for the WMD key.

Impact of Workaround: This workaround prevents users from applying skin files to Windows Media Player by double clicking on them. Users can still apply skin files that are in their default ‘skins’ directory.

Un-register Wmp.dll

  1. Un-registering the Wmp.dll registry key helps protect the affected system from attempts to exploit this vulnerability. To modify the Wmp.dll registry key, follow these steps.
  2. Click Start, click Run, type "regsvr32 -u %windir%\system32\wmp.dll" (without the quotation marks), and then click OK.
  3. When a dialog box appears that confirms that the process has been successful, click OK.
  4. Select the File Types tab.

Impact of Workaround: This workaround disables the Windows Media Player and applications that use the embedded Windows Media ActiveX Control.

FAQ for Windows Media Player Code Execution Vulnerability Decompressing Skins - CVE-2007-3035

What is the scope of the vulnerability? 
A code execution vulnerability exists in Windows Media Player skin parsing. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs or view, change, or delete data.

What causes the vulnerability? 
Windows Media Player incorrectly handles header information contained in skin files.

What is a skin file? 
Skins are sets of scripts, art, media, and text files that can be combined to create a new appearance for Windows Media Player. Using skins, you can change not only the way Windows Media Player looks, but how it functions. Windows Media Player skin files are distributed in WMZ and WMD files.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of an affected system. Users whose accounts are configured to have fewer user rights on the guest operating system are less impacted than users who operate with administrative user rights on the guest operating system.

How could an attacker exploit the vulnerability? 
In a Web-based attack scenario, an attacker could host a specially-crafted skin file designed to exploit this vulnerability through Windows Media Player and then convince a user to view the skins file. 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 an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted skin file to the user and by persuading the user to open the file.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user is logged on and opens the malicious skin file in Windows Media Player for any malicious action to occur. Therefore, any systems where Windows Media Player is 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 changing Windows Media Player to correctly handle header information contained in skin 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.

Update Information

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 at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.

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), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer and Enterprise Update Scan Tool (EST)

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.

MBSA 1.2.1 does not support detection for this security update. The Enterprise Update Scan Tool does, and is what customers can use instead of MBSA 1.2.1. For download links and more information about the version of EST that is being released this month, see Microsoft Knowledge Base Article 894193. SMS customers should also see the heading, Systems Management Server, for more information about SMS and EST.

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

SoftwareMBSA 1.2.1ESTMBSA 2.0.1
Windows Media Player 7.1YesNot ApplicableYes
Windows Media Player 9YesNot ApplicableYes
Windows Media Player 10NoYesYes
Windows Media Player 11NoNoYes

Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

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.

SoftwareSMS 2.0ESTSMS 2003
Windows Media Player 7.1YesYesYes
Windows Media Player 9YesYesYes
Windows Media Player 10Yes (with EST)YesYes
Windows Media Player 11NoNoYes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

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. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.

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

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 PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionWindowsMedia7-KB936782-nec98-JPN.exe /quiet
WindowsMedia9-KB936782-nec98-JPN.exe /quiet
WindowsMedia9-KB936782-x86-enu.exe /quiet
WindowsMedia7-KB936782-x86-enu.exe /quiet
Installing without restartingWindowsMedia7-KB936782-nec98-JPN.exe /norestart
WindowsMedia9-KB936782-nec98-JPN.exe /norestart
WindowsMedia9-KB936782-x86-enu.exe /norestart
WindowsMedia7-KB936782-x86-enu.exe /norestart
Update log fileKB936782.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredThis 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.
HotpatchingNot applicable
Removal InformationTo 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.

For Windows Media Player 7.1:
%Windir%\$NTUninstallKB936782_WMP7$\Spuninst\Spuninst.exe

For Windows Media Player 9:
%Windir%\$NTUninstallKB936782_WMP9$\Spuninst\Spuninst.exe
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationFor Windows Media Player 7.1:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 7.1\SP4\KB936782_WMP7\Filelist

For Windows Media Player 9
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 9\SP4\KB936782_WMP9\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 Player 7.1 on Windows 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSize
Wmpui.dll7.10.0.308030-Apr-200719:071,112,304

For Windows Media Player 9.0 on Windows 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSize
Wmp.dll9.0.0.335430-Apr-200709:224,734,976

Note For a complete list of supported versions and editions, 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.

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

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

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

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

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

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

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

Windows Server 2003 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionWindowsServer2003-KB936782-x86-ENU.exe /quiet

WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe /quiet

Installing without restartingWindowsServer2003-KB936782-x86-ENU.exe /norestart

WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe /norestart

Update log fileKB936782.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredThis 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.

HotpatchingNot applicable
Removal InformationTo 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.

For Windows Media Player 10 SP1 and Windows Media Player 10 SP2:
%Windir%\$NTUninstallKB936782$\Spuninst\Spuninst.exe
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationFor Windows Media Player 10 SP1:

HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB936782\Filelist

For Windows Media Player 10 SP2:

HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB936782\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 Player 10 when installed on all versions of Windows Server 2003:

File NameVersionDateTimeSizeFolder
Wmp.dll10.0.0.370925-Jun-200709:246,045,696SP1GDR
Wmp.dll10.0.0.370925-Jun-200709:036,045,696SP1QFE
Wmp.dll10.0.0.399825-Jun-200708:196,049,792SP2GDR
Wmp.dll10.0.0.399825-Jun-200709:236,049,792SP2QFE

For Windows Media Player 10 when installed on all versions of Windows Server x64 Edition:

File NameVersionDateTimeSizeCPUFolder
Wwmp.dll10.0.0.370925-Jun-200710:306,045,696X64SP1GDR\WOW
Wwmp.dll10.0.0.370925-Jun-200710:306,045,696X64SP1QFE\WOW
Wwmp.dll10.0.0.399825-Jun-200710:356,049,792X64SP2GDR\WOW
Wwmp.dll10.0.0.399825-Jun-200710:306,049,792X64SP2QFE\WOW

Note For a complete list of supported versions and editions, 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.

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

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

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

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

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

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

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

Windows XP (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionWindowsMedia9-KB936782-x86-enu.exe /quiet
WindowsMedia10-KB936782-x86-enu.exe /quiet
WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe /quiet
WindowsMedia11-KB936782-x86-enu.exe /quiet
WindowsMedia11-KB936782-x64-enu.exe /quiet
Installing without restartingWindowsMedia9-KB936782-x86-enu.exe /norestart
WindowsMedia10-KB936782-x86-enu.exe /norestart
WindowsServer2003.WindowsXP-KB936782-x64-ENU.exe /norestart
WindowsMedia11-KB936782-x86-enu.exe /norestart
WindowsMedia11-KB936782-x64-enu.exe /norestart
Update log fileKB936782.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredThis 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.
HotpatchingNot applicable
Removal InformationTo 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.

For Windows Media Player 9:
%Windir%\$NTUninstallKB936782_WMP9$\Spuninst\Spuninst.exe

For Windows Media Player 10:
%Windir%\$NTUninstallKB936782_WMP10$\Spuninst\Spuninst.exe

For Windows Media Player 11:
%Windir%\$NTUninstallKB936782_WMP11$\Spuninst\Spuninst.exe

For Windows Media Player 10 on XP Pro x64 SP2:
%Windir%\$NTUninstallKB936782$\Spuninst\Spuninst.exe
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationFor Windows Media Player 9:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 9\SP2\KB936782_WMP9\Filelist

For Windows Media Player 10:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 10\SP2\KB936782_WMP10\Filelist

For Windows Media Player 11:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 11\SP2\KB936782_WMP11\Filelist

For Windows Media Player 10 on XP Pro x64:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB936782\Filelist

For Windows Media Player 10 on XP Pro x64 SP2:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB936782\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 Player 9 when installed on all versions of Windows XP:

File NameVersionDateTimeSize
Wmp.dll9.0.0.335430-Apr-200709:224,734,976

Windows Media Player 10 when installed on all versions of Windows XP:

File NameVersionDateTimeSize
Wmp.dll10.0.0.405830-Apr-200715:205,537,792

Windows Media Player 11 when installed on all versions of Windows XP:

File NameVersionDateTimeSize
Wmp.dll11.0.5721.523012-Jun-200706:5110,834,944

For Windows Media Player 10 when installed on all versions of Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Wwmp.dll10.0.0.370925-Jun-200710:306,045,696X64SP1GDR\WOW
Wwmp.dll10.0.0.370925-Jun-200710:306,045,696X64SP1QFE\WOW
Wwmp.dll10.0.0.399825-Jun-200710:356,049,792X64SP2GDR\WOW
Wwmp.dll10.0.0.399825-Jun-200710:306,049,792X64SP2QFE\WOW

Windows Media Player 11 when installed on all versions of Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Wmp.dll11.0.5721.523012-Jun-200706:5110,834,944x64SP1GDR\WOW

Note For a complete list of supported versions and editions, 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.

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

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

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 PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionWindows6.0-KB936782-x86.msu /quiet

Windows6.0-KB936782-x64.msu /quiet

Installing without restartingWindows6.0-KB936782-x86.msu /norestart

Windows6.0-KB936782-x64.msu /norestart

Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredThis 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.

HotpatchingNot applicable
Removal InformationTo remove this update, click Control Panel, click Security, then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationNo registry key exists for Windows Media Player 11 on Windows Vista. Use Windows Management Instrumentation to detect the presence of this patch.

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 Player 11 on Windows Vista:

File NameVersionDateTimeSizeCPUFolder
wmp.dll11.0.6000.633621-Jul-200702:3010,617,344X86Windows6.0-KB936782-x86\x86_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.16529_none_0976e55551fb476e
wmp.dll11.0.6000.633621-Jul-200702:2510,616,832x86Windows6.0-KB936782-x86\x86_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.20645_none_09e6e1206b2cb9be

For Windows Media Player 11 on Windows Vista x64 Edition:

File NameVersionDateTimeSizeCPUFolder
wmp.dll11.0.6000.633621-Jul-200703:3813,585408x64Windows6.0-KB936782-x64\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.16529_none_659580d90a58b8a4
wmp.dll11.0.6000.633621-Jul-200703:2613,584896x64Windows6.0-KB936782-x64\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.20645_none_66057ca4238a2af4
wmp.dll11.0.6000.633621-Jul-200702:3010,617,344x64Windows6.0-KB936782-x64\wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.16529_none_6fea2b2b3eb97a9f
wmp.dll11.0.6000.633621-Jul-200702:2510,616,832x64Windows6.0-KB936782-x64\wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.0.6000.20645_none_705a26f657eaecef

Note For a complete list of supported versions and editions, 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.

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

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

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

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

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

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

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

Other Information

Acknowledgments

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

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 (August 14, 2007): Bulletin published.
  • V1.1 (August 29, 2007): Bulletin revised to correct Registry Key Verification for Windows Media Player 7.1, 9, 10, and 11 on supported editions of Windows 2000 Service Pack 4, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows XP Service Pack 2 and x64 Editions.
  • V1.2 (September 19, 2007): Bulletin revised to correct file information when installing without user intervention, installing without restarting, and removal Information for Windows Media Player 7.1, 9, 10, and 11 on supported editions of Windows 2000 Service Pack 4, Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows XP Service Pack 2 and x64 Editions.
  • V2.0 (August 12, 2008): Added Windows XP Service Pack 3 as affected software. 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.
  • V2.1 (September 10, 2008): Removed Windows Media Player 9 on Windows XP Service Pack 3 from the Affected Software table. This is a bulletin change only; there were no changes to detection or to the binaries. Customers who have successfully updated their systems do not need to reinstall this update.

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

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