Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Movie Maker buffer overflow

  CORE-2009-0813: Windows Movie Maker and Microsoft Producer IsValidWMToolsStream(
) Heap Overflow

From:MICROSOFT <secure_(at)_microsoft.com>
Date:10.03.2010
Subject:Microsoft Security Bulletin MS10-016 - Important Vulnerability in Windows Movie Maker Could Allow Remote Code Execution (975561)

Microsoft Security Bulletin MS10-016 - Important
Vulnerability in Windows Movie Maker Could Allow Remote Code Execution (975561)
Published: March 09, 2010

Version: 1.0
General Information
Executive Summary

This security update addresses a privately reported vulnerability in Windows Movie Maker and Microsoft Producer 2003. Windows Live Movie Maker, which is available for Windows Vista and Windows 7, is not affected by this vulnerability. The vulnerability could allow remote code execution if an attacker sent a specially crafted Movie Maker or Microsoft Producer project file and convinced the user to open the specially crafted file. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Important for Windows Movie Maker 2.1, Windows Movie Maker 2.6, Windows Movie Maker 6.0, and Microsoft Producer 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by changing the way that Windows Movie Maker parses project files. There is no security update available for Microsoft Producer 2003 at this time. Customers can mitigate the impact to systems with Microsoft Producer 2003 by applying the automated solution to remove the Microsoft Producer file associations using the Fix it found in Microsoft Knowledge Base Article 975561, and by applying the workarounds in this bulletin. 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. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

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

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

Known Issues. Microsoft Knowledge Base Article 975561 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
Top of sectionTop of section
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 XP Service Pack 2 and Windows XP Service Pack 3


Movie Maker 2.1[1]


Remote Code Execution


Important


None

Windows XP Professional x64 Edition Service Pack 2


Movie Maker 2.1[1]


Remote Code Execution


Important


None

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Movie Maker 6.0[1]

Movie Maker 2.6[2]


Remote Code Execution


Important


None

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Movie Maker 6.0[1]

Movie Maker 2.6[2]


Remote Code Execution


Important


None

Windows 7 for 32-bit Systems


Movie Maker 2.6[2]


Remote Code Execution


Important


None

Windows 7 for x64-based Systems


Movie Maker 2.6[2]


Remote Code Execution


Important


None


[1]These versions of Windows Movie Maker are delivered with the indicated operating systems.

[2]Windows Movie Maker 2.6 is an optional download that can be installed on the indicated operating systems. Windows 7 systems without Movie Maker 2.6 installed are not affected.

Affected Software
Other Office Software Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update

Microsoft Producer 2003[3]


Remote Code Execution


Important


None

[3]The security update for Microsoft Producer 2003 is unavailable at this time. Customers can mitigate the impact to systems with Microsoft Producer 2003 by removing the Microsoft Producer file associations using the automated solution found in Microsoft Knowledge Base Article 975561, and by applying the workarounds in this bulletin.

Non-Affected Software
Software

Microsoft Windows 2000 Service Pack 4

Windows Server 2003 Service Pack 2

Windows Server 2003 x64 Edition Service Pack 2

Windows Server 2003 with SP2 for Itanium-based Systems

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2

Windows 7 for 32-bit Systems

Windows 7 for x64-based Systems

Windows Server 2008 R2 for x64-based Systems

Windows Server 2008 R2 for Itanium-based Systems

Windows Live Movie Maker
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

Where is the update for Microsoft Producer 2003?
A security update for Microsoft Producer 2003 is unavailable at this time. Microsoft recommends that customers using Microsoft Producer 2003 uninstall the Microsoft Producer add-in software. Customers can mitigate the impact to systems with Microsoft Producer 2003 by applying an automated solution found in Microsoft Knowledge Base Article 975561 to remove the Microsoft Producer file associations, or they can use the workarounds provided in this security bulletin.

What is Microsoft Producer 2003?
Microsoft Producer 2003 is a downloadable add-in component for Microsoft Office PowerPoint 2002 and Microsoft Office PowerPoint 2003. Microsoft Producer 2003 is not installed by default. Microsoft Producer 2003 provides users with many features that make it easier to synchronize audio, video, slides, and images to create rich-media presentations that are viewable in a browser.

How can I determine the version of Windows Movie Maker installed on my system?
To determine your version of Movie Maker, launch Movie Maker from the Start menu, click Help, and then click About.

Is it possible to have more than one version of Windows Movie Maker installed on a single computer?
Yes, on Microsoft Vista, you will have Movie Maker 6.0 which was delivered with the operating system, and you might have also installed Windows Movie Maker 2.6, which is a separate download. In this case, both versions of Movie Maker will be detected and offered the security update.

On Windows 7, it is possible to install both Movie Maker 2.6 and Windows Live Movie Maker, a separate product which is part of Windows Live Essentials. If you have installed the software, Movie Maker 2.6 will be offered the security update, but Windows Live Movie Maker is not affected and will not be offered this security update.

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

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

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 in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the March bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Movie Maker and Producer Buffer Overflow Vulnerability – CVE-2010-0265 Aggregate Severity Rating

Windows Movie Maker 2.1 on Windows XP Service Pack 2 and Windows XP Service Pack 3


Important
Remote Code Execution


Important

Windows Movie Maker 2.1 on Windows XP Professional x64 Edition Service Pack 2


Important
Remote Code Execution


Important

Windows Movie Maker 6.0 on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Important
Remote Code Execution


Important

Windows Movie Maker 6.0 on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Important
Remote Code Execution


Important

Windows Movie Maker 2.6 when installed on Windows Vista


Important
Remote Code Execution


Important

Windows Movie Maker 2.6 when installed on Windows 7


Important
Remote Code Execution


Important

Microsoft Producer 2003


Important
Remote Code Execution


Important
Top of sectionTop of section

Movie Maker and Producer Buffer Overflow Vulnerability - CVE-2010-0265

A remote code execution vulnerability exists in the way that Windows Movie Maker and Microsoft Producer 2003 handle specially crafted project files. 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.

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

Mitigating Factors for Movie Maker and Producer Buffer Overflow Vulnerability - CVE-2010-0265

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


In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to 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.


The specially crafted file could be sent as an e-mail attachment, but the attacker would have to convince the user to open the attachment in order to exploit the vulnerability.


An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Top of sectionTop of section

Workarounds for Movie Maker Buffer Overflow Vulnerability - CVE-2010-0265

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:


Remove the Movie Maker .MSWMM file association

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

Note We recommend backing up the registry before you edit it.

To remove the Movie Maker .MSWMM file association, follow these steps:

Interactive Method

1.


Click Start, click Run, type regedit, and then click OK.

2.


Expand HKEY_CLASSES_ROOT, click on .MSWMM, and then click the Registry menu and select Export.

3.


In the Export Registry File dialog box, type MSWMM file association registry backup.reg and click 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. When prompted to delete the registry value, click Yes.

Managed Deployment Script

1.


Make a backup copy of the registry key using the following command:

Regedit.exe /e MSWMM_registry_backup.reg HKEY_CLASSES_ROOT\.MSWMM

2.


Save the following to a file with a .REG extension (i.e., Delete_MSWMM_file_association.reg):

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\.MSWMM]

3.


Run the registry script created in step 2 on the target machine with the following command:

Regedit.exe /s Delete_MSWMM_file_association.reg

Impact of workaround. This workaround removes the .MSWMM file association. Double-clicking an MSWMM file will no longer launch Windows Movie Maker.

How to undo the workaround. Restore the registry key by using Regedit to restore the settings saved in the .REG file.


Remove the Microsoft Producer 2003 .MSProducer, .MSProducerZ, and .MSProducerBF file associations

Note See Microsoft Knowledge Base Article 975561 to use the automated Microsoft Fix it solution to enable or disable this workaround.

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

Note We recommend backing up the registry before you edit it.

To remove the .MSProducer, .MSProducerZ, and .MSProducerBF file associations, follow these steps:

Interactive Method

1.


Click Start, click Run, type regedit, and then click OK.

2.


Expand HKEY_CLASSES_ROOT, click on .MSProducer, and then click the Registry menu and select Export.

3.


In the Export Registry File dialog box, type MSProducer file association registry backup.reg and click 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. When prompted to delete the registry value, click Yes.

5.


Repeat steps 2-4 for the .MSProducerZ and .MSProducerBF file associations.

Managed Deployment Script

1.


Make a backup copy of the registry key using the following command:

Regedit.exe /e MSProducer_registry_backup.reg HKEY_CLASSES_ROOT\.MSProducer

2.


Save the following to a file with a .REG extension (i.e., Delete_MSProducer_file_association.reg):

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\.MSProducer]

3.


Run the registry script created in step 2 on the target machine with the following command:

Regedit.exe /s Delete_MSProducer_file_association.reg

4.


Repeat steps 1-3 for the .MSProducerZ and .MSProducerBF file associations.

Impact of workaround. This workaround removes the .MSProducer, .MSProducerZ, and .MSProducerBF file associations. Double-clicking Microsoft Producer 2003 files will no longer launch Microsoft Producer 2003.

How to undo the workaround. Restore the registry keys by using Regedit to restore the settings saved in the .REG files.


Disable Microsoft Producer 2003 by restricting access

An administrator can apply an access control list to Microsoft Producer to ensure that the add-in can no longer be loaded. This effectively prevents exploitation of the vulnerability using this attack vector.

For Windows XP for 32-bit Systems

Run the following command from a command prompt:

cacls "%programfiles%\microsoft producer 2\producer.exe" /E /P everyone:N

For Windows XP for x64-based Systems

Run the following command from a command prompt:

cacls "%programfiles(x86)%\microsoft producer 2\producer.exe" /E /P everyone:N

Impact of workaround.Upon implementing the workaround, the user will no longer be able to run Microsoft Producer 2003.

How to undo the workaround. An administrator can run the following commands to allow the Microsoft Producer 2003 add-in to be loaded.

For Windows XP for 32-bit Systems

Run the following command from a command prompt:

cacls "%programfiles%\microsoft producer 2\producer.exe" /E /R everyone

For Windows XP for x64-based Systems

Run the following command from a command prompt:

cacls "%programfiles(x86)%\microsoft producer 2\producer.exe" /E /R everyone


Prevent Microsoft Producer 2003 from being installed

An administrator can apply an access control list for Microsoft Producer 2003 to ensure that the Microsoft Producer 2003 add-in cannot be installed. This effectively prevents exploitation of the vulnerability using this attack vector.

For Windows XP for 32-bit Systems

Run the following commands from a command prompt:

md "%programfiles%\microsoft producer 2"

echo Placeholder > "%programfiles%\microsoft producer 2\producer.exe"

cacls "%programfiles%\microsoft producer 2\producer.exe" /E /P everyone:N

For Windows XP for x64-based Systems

Run the following commands from a command prompt:

md "%programfiles(x86)%\microsoft producer 2"

echo Placeholder > "%programfiles(x86)%\microsoft producer 2\producer.exe"

cacls "%programfiles(x86)%\microsoft producer 2\producer.exe" /E /P everyone:N

Impact of workaround. Upon implementing the workaround, users will no longer be able to install the Microsoft Producer 2003 add-in.

How to undo the workaround. An administrator can run the following commands to allow the Microsoft Producer 2003 add-in to be installed.

For Windows XP for 32-bit Systems

Run the following commands from a command prompt:

cacls "%programfiles%\microsoft producer 2\producer.exe" /E /R everyone

echo y| del "%programfiles%\microsoft producer 2\producer.exe"

For Windows XP for x64-based Systems

Run the following commands from a command prompt:

cacls "%programfiles(x86)%\microsoft producer 2\producer.exe" /E /R everyone

echo y| del "%programfiles(x86)%\microsoft producer 2\producer.exe"


Uninstall Microsoft Producer 2003

Use Add/Remove Programs to uninstall Microsoft Producer 2003.

Impact of workaround. Upon implementing the workaround, users will no longer be able to run Microsoft Producer 2003.
Top of sectionTop of section

FAQ for Movie Maker and Producer Buffer Overflow Vulnerability - CVE-2010-0265

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

What causes the vulnerability?
The vulnerability exists in the way that Windows Movie Maker and Microsoft Producer 2003 parse the project file formats. This vulnerability requires a malicious user to send a specially crafted Movie Maker or Producer file and convince the user to open the specially crafted file.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Movie Maker or Producer project file to the user and by convincing the user to open the file.

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

How could an attacker exploit the vulnerability?
Exploitation of this vulnerability requires that a user open a specially crafted Movie Maker or Producer project file with an affected version of Windows Movie Maker or Microsoft Producer.

What systems are primarily at risk from the vulnerability?
Windows systems where either Windows Movie Maker is used, or systems where Microsoft Producer 2003 is used, are primarily at risk.

What does the update do?
This update addresses the vulnerability by changing the way that Windows Movie Maker parses Windows Movie Maker project files. No update is available for Microsoft Producer 2003 at this time.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section
Update Information

Detection and Deployment Tools and Guidance

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

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

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

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

Detection and Deployment Guidance

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

Microsoft Baseline Security Analyzer

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

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

Windows XP Service Pack 2 and Windows XP Service Pack 3


Yes

Windows XP Professional x64 Edition Service Pack 2


Yes

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Yes

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Yes

Windows 7 for 32-bit Systems


Yes

Windows 7 for x64-based Systems


Yes

The latest version of MBSA has been released: Microsoft Baseline Security Analyzer 2.1.1. For more information, see Microsoft Baseline Security Analyzer 2.1.

Windows Server Update Services

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

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.
Software SMS 2.0 SMS 2003 with SUIT SMS 2003 with ITMU Configuration Manager 2007

Windows XP Service Pack 2 and Windows XP Service Pack 3


Yes


Yes


Yes


Yes

Windows XP Professional x64 Edition Service Pack 2


No


No


Yes


Yes

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


No


No


Yes


Yes

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


No


No


Yes


Yes

Windows 7 for 32-bit Systems


No


No


Yes


Yes

Windows 7 for x64-based Systems


No


No


Yes


Yes

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

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. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

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

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

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

Update Compatibility Evaluator and Application Compatibility Toolkit

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

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

Security Update Deployment

Affected Software

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

Windows XP (all editions)

Reference Table

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

Inclusion in Future Service Packs


The update for this issue will be included in a future service pack or update rollup

Deployment




Installing without user intervention


For Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB975561-x86-enu /quiet




For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB975561-x64-enu /quiet

Installing without restarting


For Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB975561-x86-enu /norestart




For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB975561-x64-enu /norestart

Update log file


KB975561.log

Further information


See the subsection, Detection and Deployment Tools and Guidance

Restart Requirement




Restart required?


In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

HotPatching


Not applicable

Removal Information


Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB975561$\Spuninst folder

File Information


See Microsoft Knowledge Base Article 975561

Registry Key Verification


For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB975561\Filelist




For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB975561\Filelist

Note This security update does not apply to Windows Server 2003 x64 Edition because Windows Movie Maker cannot be installed on that operating system.

Deployment Information

Installing the Update

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

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

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

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

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/help


Displays the command-line options.
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed.

/forcerestart


Restarts the computer after installation and force other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart.
Special Options

/overwriteoem


Overwrites OEM files without prompting.

/nobackup


Does not back up files needed for uninstall.

/forceappsclose


Forces other programs to close when the computer shuts down.

/log:path


Allows the redirection of installation log files.

/integrate:path


Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

/extract[:path]


Extracts files without starting the Setup program.

/ER


Enables extended error reporting.

/verbose


Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Removing the Update

This security update supports the following setup switches.
Supported Spuninst.exe Switches
Switch Description

/help


Displays the command-line options.
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and force other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart.
Special Options

/forceappsclose


Forces other programs to close when the computer shuts down.

/log:path


Allows the redirection of installation log files.

Verifying That the Update Has Been Applied


Microsoft Baseline Security Analyzer

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


File Version Verification

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

1.


Click Start, and then click Search.

2.


In the Search Results pane, click All files and folders under Search Companion.

3.


In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4.


In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.

5.


On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

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


Registry Key Verification

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

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

Windows Vista (all editions)

Reference Table

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

Inclusion in Future Service Packs


The update for this issue will be included in a future service pack or update rollup

Deployment




Installing without user intervention


For Windows Movie Maker 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB975561-x86 /quiet




For Windows Movie Maker 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB975561-x64 /quiet




For Movie Maker 2.6 when installed on all supported 32-bit and x64-based editions of Windows Vista:
MM26-KB975561 /quiet

Installing without restarting


For Windows Movie Maker 6.0 on all supported 32-bit editions of Windows Vista:
Windows6.0-KB975561-x86 /quiet /norestart




For Windows Movie Maker 6.0 on all supported x64-based editions of Windows Vista:
Windows6.0-KB975561-x64 /quiet /norestart




For Movie Maker 2.6 when installed on all supported 32-bit and x64-based editions of Windows Vista:
MM26-KB975561 /quiet /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 Microsoft Knowledge Base Article 975561

Registry Key Verification


For Windows Movie Maker 6.0, a registry key does not exist to validate the presence of this update.




For Movie Maker 2.6 on Windows Vista:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-
18\Products\F45FAD3B52BD6854E91F692DB41B0488\Patches\13161686A7BC
5874791FCB0C57C2A9DF

Deployment Information

Installing the Update

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

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

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/?, /h, /help


Displays help on supported switches.

/quiet


Suppresses the display of status or error messages.

/norestart


When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

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

Verifying That the Update Has Been Applied


Microsoft Baseline Security Analyzer

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


File Version Verification

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

1.


Click Start and then enter an update file name in Start Search.

2.


When the file appears under Programs, right-click on the file name and click Properties.

3.


Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.

4.


You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

5.


Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Top of sectionTop of section
Top of sectionTop of section

Windows 7

Reference Table

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

Inclusion in Future Service Packs


The update for this issue will be included in a future update

Deployment




Installing without user intervention


For Movie Maker 2.6 when installed on Windows 7:
MM26-KB975561 /quiet

Installing without restarting


For Movie Maker 2.6 when installed on Windows 7:
MM26-KB975561 /quiet /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 Microsoft Knowledge Base Article 975561

Registry Key Verification


For Movie Maker 2.6 on Windows 7:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-
18\Products\F45FAD3B52BD6854E91F692DB41B0488\Patches\13161686A7BC
5874791FCB0C57C2A9DF

Deployment Information

Installing the Update

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

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

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/?, /h, /help


Displays help on supported switches.

/quiet


Suppresses the display of status or error messages.

/norestart


When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

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

Verifying That the Update Has Been Applied


Microsoft Baseline Security Analyzer

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


File Version Verification

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

1.


Click Start and then enter an update file name in Start Search.

2.


When the file appears under Programs, right-click on the file name and click Properties.

3.


Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.

4.


You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

5.


Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section
Other Information
Acknowledgements

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


Damián Frizza of Core Security Technologies for reporting the Movie Maker and Producer Buffer Overflow Vulnerability (CVE-2010-0265)
Top of sectionTop of section
Microsoft Active Protections Program (MAPP)

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


Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.


International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

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

Revisions


V1.0 (March 9, 2010): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod