Export (0) Print
Expand All

Microsoft Security Bulletin MS09-033 - Important

Vulnerability in Virtual PC and Virtual Server Could Allow Elevation of Privilege (969856)

Published: July 14, 2009 | Updated: March 09, 2010

Version: 2.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft Virtual PC and Microsoft Virtual Server. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected guest operating system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

This security update is rated Important for all supported editions of Virtual PC 2004, Virtual PC 2007, and Virtual Server 2005. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by enforcing validation of privilege levels when executing machine instructions. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. Microsoft Knowledge Base Article 969856 documents the currently known issues that customers may experience when installing this security update.

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

SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Virtual PC 2004 Service Pack 1
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual PC 2007
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual PC 2007 Service Pack 1
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual PC 2007 x64 Edition
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual PC 2007 x64 Edition Service Pack 1
(KB969856)
Elevation of PrivilegeImportant None 
Microsoft Virtual Server 2005
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual Server 2005 R2 Service Pack 1
(KB969856)
Elevation of PrivilegeImportantNone
Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1
(KB969856)
Elevation of PrivilegeImportantNone

Non-Affected Software

Software
Microsoft Virtual PC for Mac 7.1

Why was this bulletin rereleased on March 9, 2010? 
Microsoft rereleased this bulletin to add Microsoft Virtual Server 2005 to affected software. Customers running Microsoft Virtual Server 2005 on supported editions of Microsoft Windows should consider applying the security update. No other update packages are affected by this rerelease.

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.

What are the known issues that customers may experience when installing this security update? 
Microsoft Knowledge Base Article 969856 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 have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

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

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

Vulnerability Information

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareVirtual PC and Virtual Server Privileged Instruction Decoding Vulnerability - CVE-2009-1542Aggregate Severity Rating
Microsoft Virtual PC 2004 Service Pack 1 Important 
Elevation of Privilege
Important
Microsoft Virtual PC 2007 and Microsoft Virtual PC 2007 Service Pack 1 Important 
Elevation of Privilege
Important
Microsoft Virtual PC 2007 x64 Edition and Microsoft Virtual PC 2007 x64 Edition Service Pack 1 Important 
Elevation of Privilege
Important
Microsoft Virtual Server 2005 Important 
Elevation of Privilege
Important
Microsoft Virtual Server 2005 R2 Service Pack 1 Important 
Elevation of Privilege
Important
Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Important 
Elevation of Privilege
Important

An elevation of privilege vulnerability exists in the way that Microsoft Virtual PC and Microsoft Virtual Server incorrectly validate privilege levels when executing specific instructions in the Virtual Machine Monitor. This vulnerability could allow an attacker to run code with elevated privileges inside the hosted guest operating system. An attacker could then install programs; view, change, or delete data; or create new accounts on the guest operating system with full user rights.

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

Mitigating Factors for Virtual PC and Virtual Server Privileged Instruction Decoding Vulnerability - CVE-2009-1542

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

  • An attacker must be authenticated and logged in to the guest operating system running in the virtual machine in order to exploit this vulnerability.
  • Windows Server 2008 Hyper-V is not affected by this vulnerability.
  • Windows Virtual PC and Windows XP Mode on Windows 7 are not affected by this vulnerability.
  • Deployments using Hardware Assisted Virtualization (HAV) are not affected by this vulnerability. HAV is supported by Virtual PC 2007 and Virtual Server 2005 R2 SP1, but on these versions HAV needs to be explicitly enabled.

Workarounds for Virtual PC and Virtual Server Privileged Instruction Decoding Vulnerability - CVE-2009-1542

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Virtual PC and Virtual Server Privileged Instruction Decoding Vulnerability - CVE-2009-1542

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability in Microsoft Virtual PC and Microsoft Virtual Server. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of a guest operating system hosted in a virtual machine by one of the affected products. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability? 
Virtual PC and Virtual Server do not correctly validate whether specific machine instructions require a minimum CPU privilege level in order to run within the guest operating system environment. This may allow user mode applications to execute instructions which should only be issued in kernel mode.

What are Microsoft Virtual PC and Virtual Server? 
Microsoft Virtual PC allows customers to create and run one or more virtual machines, each with its own operating system, on a single computer. It creates a virtualized environment that runs a guest operating system. Microsoft Virtual Server, on the other hand, is a similar solution for server operating systems.

What is the Virtual Machine Monitor (VMM)? 
The Virtual Machine Monitor (VMM) component of Virtual Server 2005 is a kernel-mode driver running on the host operating system. VMM has limited and specific functionality, acting as a firewall between the host operating system and virtual machines. VMM has access to the physical computer processor and manages resources between the two environments, preventing malicious or poorly designed applications running in a guest operating system from requesting excessive hardware resources from the host operating system.

What is Hardware Assisted Virtualization (HAV)? 
Hardware Assisted Virtualization is a technology that allows the processor to support the virtualization directly as opposed to virtualization being achieved entirely in software. HAV is available in processors that include a virtualization option; specifically, Intel VT or AMD Virtualization. Deployments configured to use Hardware Assisted Virtualization are not affected by this vulnerability.

Can this vulnerability be leveraged to compromise the host operating system? 
No. This vulnerability can only allow elevation of privilege within the guest operating system. It does not allow an attacker to escape from the virtualized environment into the host operating system or any other guest operating systems hosted by the same Virtual Server or Virtual PC installation.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run code with elevated privileges on the guest operating system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights on the guest operating system.

How could an attacker exploit the vulnerability? 
To exploit this vulnerability, an attacker would first have to log on to the guest virtual machine. An attacker could then run a specially crafted application that could exploit the vulnerability and elevate privileges within the virtual machine environment.

What systems are primarily at risk from the vulnerability? 
Guest operating systems hosting virtual machines that allow authenticated users to execute custom binaries are at the most risk from this vulnerability.

What does the update do? 
The update addresses the vulnerability by enforcing validation of the required privilege levels when executing specific machine instructions on the guest operating system.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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

Update Information

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

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

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

Note Starting August 1, 2009, Microsoft will discontinue support for Office Update and the Office Update Inventory Tool. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About 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
Microsoft Virtual PC 2004 Service Pack 1Yes
Microsoft Virtual PC 2007 and Microsoft Virtual PC 2007 Service Pack 1Yes
Microsoft Virtual PC 2007 x64 Edition and Microsoft Virtual PC 2007 x64 Edition Service Pack 1Yes
Microsoft Virtual Server 2005Yes
Microsoft Virtual Server 2005 R2 Service Pack 1Yes
Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1Yes

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

Windows Server Update Services

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

Systems Management Server

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

SoftwareSMS 2.0SMS 2003 with SUSFPSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Virtual PC 2004 Service Pack 1NoNoYesYes
Microsoft Virtual PC 2007 and Microsoft Virtual PC 2007 Service Pack 1NoNoYesYes
Microsoft Virtual PC 2007 x64 Edition and Microsoft Virtual PC 2007 x64 Edition Service Pack 1NoNoYesYes
Microsoft Virtual Server 2005NoNoYesYes
Microsoft Virtual Server 2005 R2 Service Pack 1NoNoYesYes
Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1NoNo YesYes

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

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

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

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

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

Update Compatibility Evaluator and Application Compatibility Toolkit

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

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

Affected Software

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

Microsoft Virtual PC (all editions)

Reference Table

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

Inclusion in Future Service Packs The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention*For Virtual PC 2004 Service Pack 1:
VPC2004x86-KB969856 /Q:A /R:A
For Virtual PC 2007:
vpc2007nospx86-KB969856 /Q:A /R:A
For Virtual PC 2007 Service Pack 1:
VPC2007x86-KB969856 /Q:A /R:A
For Virtual PC 2007 x64 Edition:
VPC2007nospx64-KB969856 /Q:A /R:A
For Virtual PC 2007 x64 Edition Service Pack 1:
VPC2007x64-KB969856 /Q:A /R:A
Installing without restarting*For Virtual PC 2004 Service Pack 1:
VPC2004x86-KB969856 /R:N
For Virtual PC 2007:
vpc2007nospx86-KB969856 /R:N
For Virtual PC 2007:
vpc2007x86-KB969856 /R:N
For Virtual PC 2007 x64 Edition:
vpc2007nospx64-KB969856 /R:N
For Virtual PC 2007 x64 Edition Service Pack 1:
vpc2007x64-KB969856 /R:N
Update log fileThis security update does not generate a log file.
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?This update does not force a restart. However, the system must be restarted after you apply this security update.
HotPatchingNot applicable
Removal Information This update cannot be uninstalled.
File Information See Microsoft Knowledge Base Article 969856
Registry Key Verification For Virtual PC 2004 Service Pack 1 the following keys will be updated to contain the value VSPatcher2:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\EDDFACCCCECE4EA4DB79400767BB4D9A\Patches
For Virtual PC 2007 the following keys will be updated to contain the value VSPatcher2:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\42AAC7A832B7B0147A3C9F490B491406\Patches
For Virtual PC 2007 Service Pack 1 the following keys will be added to contain the value VSPatcher2:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\899384DAA9E2504438FFE605A34FC9BB\Patches
For Virtual PC 2007 x64 Edition the following keys will be updated to contain the value VSPatcher2:

SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\42AAC7A832B7B0147A3C9F490B491406\Patches

For Virtual PC 2007 x64 Edition Service Pack 1 the following keys will be updated to contain the value VSPatcher2:

SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\899384DAA9E2504438FFE605A34FC9BB\Patches

* To install this security update on Windows Vista and Windows Server 2008, the command listed must be issued at an elevated command prompt.

Deployment Information

Installing the Update

When you install this security update, the IExpress 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 IExpress Technology and the IExpress Wizard Web Site.

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

Microsoft Knowledge Base Article 937987 documents the currently known installation issues that customers may experience when they install this security update.

This security update supports the following IExpress batch-mode setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/Q Specifies quiet mode, or suppresses prompts, when files are being extracted. This switch does not suppress prompts when Windows Update Setup is running.
/Q:U Specifies user-quiet mode, which presents some dialog boxes to the user.
/Q:A Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/C:<UNC location> Specifies the path and name of the Setup .inf or .exe file.
Restart Options
/R:N Never restarts the computer after installation.
/R:A Always restarts the computer after installation.
/R:S Restarts the computer after installation without prompting the user.
Special Options
/T:<directory path> Specifies the target folder for extracting 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.

Microsoft Virtual Server (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 Microsoft Virtual Server 2005
VSPatcherPackage /Q:A /R:A

For Microsoft Virtual Server 2005 R2 Service Pack 1:
VSR2SP1x86-KB969856 /Q:A /R:A
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1:
VSR2SP1x64-KB969856 /Q:A /R:A
Installing without restarting*For Microsoft Virtual Server 2005
VSPatcherPackage /Q:A /R:N

For Microsoft Virtual Server 2005 R2 Service Pack 1:
VSR2SP1x86-KB969856 /Q:A /R:N
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1:
VSR2SP1x64-KB969856 /Q:A /R:N
Update log fileThis security update does not generate a log file.
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredThis update does not force a restart. However, you must restart your system after you apply this security update.
HotpatchingNot applicable
Removal Information This update cannot be uninstalled.
File Information See Microsoft Knowledge Base Article 969856
Registry Key Verification For Microsoft Virtual Server 2005 the following keys will be updated to contain the value VSPatcher2:
For Microsoft Virtual Server 2005 Standard English:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0EEDF7F0258333042A16F38A4BEC64C6\Patches
For Microsoft Virtual Server 2005 Enterprise English: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\813ACF1D304B0FB43A2E440E1CF2ADD3\Patches
For Microsoft Virtual Server 2005 Japanese Standard:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\67EC4B5345C7E7347BBA24CFF8B977B6\Patches
 For Microsoft Virtual Server 2005 Japanese Enterprise:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\C31148E7379AA7C48BF2343AB582C3D8\Patches

For Microsoft Virtual Server 2005 R2 Service Pack 1 the following keys will be updated to contain the value VSPatcher2:
For Microsoft Virtual Server 2005 R2 Service Pack 1 English:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\768AAF4834783C442BE25B1A2554D677\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 German:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\78E7565DCB7C3F1409840ABE6BD73D72\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 French:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\1564FD1449118534EAFC0F458C453F81\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Spanish:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\2F598CAFD9B2D6949A77CB0A209E2C51\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Chinese Traditional:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\FBF422F166A57814482C340036E05BCF\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Chinese Simplified:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\01B423623BBEB0D439ADE29D86248D9A\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Korean:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\65963AA892F7D564C982F9302F3938E3\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Japanese:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7A81E3C1F71412940819C794C70C8253\Patches
For Microsoft Virtual Server 2005 R2 Service Pack 1 Italian:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\D361C262BA2549146AA45A6E7AC97B8D\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 the following keys will be updated to contain the value VSPatcher2:
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 English:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\768AAF4834783C442BE25B1A2554D677\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 German:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\78E7565DCB7C3F1409840ABE6BD73D72\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 French:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\1564FD1449118534EAFC0F458C453F81\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Spanish:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\2F598CAFD9B2D6949A77CB0A209E2C51\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Chinese Traditional:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\FBF422F166A57814482C340036E05BCF\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Chinese Simplified:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\01B423623BBEB0D439ADE29D86248D9A\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Korean:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\65963AA892F7D564C982F9302F3938E3\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Japanese:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7A81E3C1F71412940819C794C70C8253\Patches
For Microsoft Virtual Server 2005 R2 x64 Edition Service Pack 1 Italian:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\D361C262BA2549146AA45A6E7AC97B8D\Patches

* To install this security update on Windows Vista and Windows Server 2008, the command listed must be issued at an elevated command prompt.

Deployment Information

Installing the Update

When you install this security update, the IExpress 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 IExpress Technology and the IExpress Wizard Web Site.

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

Microsoft Knowledge Base Article 937987 documents the currently known installation issues that customers may experience when they install this security update.

This security update supports the following IExpress batch-mode setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/Q Specifies quiet mode, or suppresses prompts, when files are being extracted. This switch does not suppress prompts when Windows Update Setup is running.
/Q:U Specifies user-quiet mode, which presents some dialog boxes to the user.
/Q:A Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/C:<UNC location> Specifies the path and name of the Setup .inf or .exe file.
Restart Options
/R:N Never restarts the computer after installation.
/R:A Always restarts the computer after installation.
/R:S Restarts the computer after installation without prompting the user.
Special Options
/T:<directory path> Specifies the target folder for extracting files.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

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

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

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

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

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

Other Information

Acknowledgments

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

  • Julien Tinnes and Tavis Ormandy of Google Inc. for reporting the Virtual PC and Virtual Server Privileged Instruction Decoding Vulnerability (CVE-2009-1542)

Microsoft Active Protections Program (MAPP)

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

Support

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

Disclaimer

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

Revisions

  • V1.0 (July 14, 2009): Bulletin published.
  • V1.1 (July 15, 2009): Added command line instructions for Windows Vista and Windows Server 2008. Also removed erroneous entry of update log file.
  • V2.0 (March 9, 2010): Rereleased this bulletin to add Microsoft Virtual Server 2005 to affected software. No other update packages are affected by this rerelease.

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft