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

Microsoft Security Bulletin MS12-062 - Important

Vulnerability in System Center Configuration Manager Could Allow Elevation of Privilege (2741528)

Published: September 11, 2012 | Updated: November 13, 2012

Version: 1.2

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft System Center Configuration Manager. The vulnerability could allow elevation of privilege if a user visits an affected website by way of a specially crafted URL. An attacker would have no way to force users to visit such a website. Instead, an attacker would have to persuade users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.

This security update is rated Important for all supported editions of Microsoft Systems Management Server 2003 and Microsoft System Center Configuration Manager 2007. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by modifying the way that System Center Configuration Manager handles specially crafted requests. 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 2741528 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

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, see Microsoft Support Lifecycle.

Affected Software 

SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Systems Management Server 2003 Service Pack 3 [1]
(KB2733631)
Elevation of PrivilegeImportantNone
Microsoft System Center Configuration Manager 2007 Service Pack 2 [1]
(KB2721642)
Elevation of PrivilegeImportantNone

[1]This update is available from the Microsoft Download Center only. 

Non-Affected Software

Software
Microsoft System Center 2012 Configuration Manager

Why was this bulletin revised on November 13, 2012? 
Microsoft revised this bulletin to rerelease the KB2721642 update for System Center Configuration Manager 2007 to address an issue in which if a customer had one or more localized versions installed, and then installed the KB2721642 update, the update overwrote the original localized resource files of the localized version(s) with English resource files.

I have already successfully installed the original KB2721642 update. Do I need to apply the KB2721642 update packages rereleased on November 13, 2012?  
If you installed the original EN (English) version of the KB2721642 update and you did not install any localized version of the update, you do not need to take any action. The rerelease update scenario does not apply to you.

If you installed one or more localized versions of the KB2721642 update, you should reinstall the appropriate refreshed localized update or updates because the original localized update packages incorrectly contained English resource files instead of the proper localized resource files.

If you have not already installed the KB2721642 update, you should install the appropriate refreshed package or packages.

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.

Where are the hashes of the security updates? 
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2741528.

Does the vulnerability described in this bulletin affect System Center Configuration Manager 2007 R2 and R3 installations , and Systems Management Server 2003 R2 installations? 
Yes. Systems running System Center Configuration Manager 2007 R2 or R3 are affected with the same severity rating as systems running System Center Configuration Manager 2007 Service Pack 2. Systems running Systems Management Server 2003 R2 are affected with the same severity rating as systems running Systems Management Server 2003 Service Pack 3. Customers should apply the appropriate security update package, KB2733631 or KB2721642, for their software.

Note System Center Configuration Manager 2007 R2 can be installed on System Center Configuration Manager 2007 Service Pack 1. System Center Configuration Manager 2007 Service Pack 1 is past the end of its support life cycle. Customers need to be at System Center Configuration Manager 2007 Service Pack 2 for the KB2721642 update package to install.

Note Systems Management Server 2003 R2 can be installed on Systems Management Server 2003 Service Pack 2. Systems Management Server 2003 Service Pack 2 is past the end of its support life cycle. Customers need to be at Systems Management Server 2003 Service Pack 3 for the KB2733631 update package to install.

Which server roles require these updates? Do they need to be installed on Branch Distribution Points?  
The KB2733631 update for Systems Management Server 2003 Service Pack 3 and the KB2721642 update for System Center Configuration Manager 2007 Service Pack 2 are server side updates and should be applied to all primary and secondary site servers. These updates do not apply to administrator consoles, clients, or to Branch Distribution Points (BDP).

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, see the Microsoft Support Lifecycle website.

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 Service Pack Lifecycle Support Policy.

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, see the Microsoft Worldwide Information website, 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.

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 September bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareReflected XSS Vulnerability - CVE-2012-2536Aggregate Severity Rating
Microsoft Systems Management Server 2003 Service Pack 3 Important 
Elevation of Privilege
Important
Microsoft System Center Configuration Manager 2007 Service Pack 2 Important 
Elevation of Privilege
Important

A cross-site scripting (XSS) vulnerability exists in System Center Configuration Manager where code can be injected back to the user in the resulting page, effectively allowing attacker-controlled code to run in the context of the user clicking the link.

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

Mitigating Factors for Reflected XSS Vulnerability - CVE-2012-2536

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 website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites 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 websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.

Workarounds for Reflected XSS Vulnerability - CVE-2012-2536

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:

  • Enable Internet Explorer 8 and Internet Explorer 9 XSS filter in the Local intranet security zone

    You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

    Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.

    How to undo the workaround.

    To undo this workaround, perform the following steps.

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

FAQ for Reflected XSS Vulnerability - CVE-2012-2536

What is the scope of the vulnerability? 
This is a cross-site scripting vulnerability that could result in elevation of privilege.

What causes the vulnerability? 
This vulnerability is caused when System Center Configuration Manager improperly handles specially crafted requests that allow an attacker to gain access to System Center Configuration Manager and carry out the same actions as an authenticated user.

What is cross-site scripting ? 
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script code into a user's session with a website. The vulnerability can affect web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include maliciously supplied content in the dynamic pages. This can allow specially crafted script to be executed. Web browsers may perpetuate this problem through their assumptions of "trusted" sites and their use of cookies to maintain persistent state with the websites that they frequent. An XSS attack inserts new, specially crafted script that can execute at the browser in the context that is associated with a trusted server.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could inject a client-side script in the user's browser. The script could spoof content, disclose information, or take any action that the user could take on the affected website on behalf of the targeted user.

How could an attacker exploit the vulnerability? 
An attacker could exploit this vulnerability by having a user visit an affected website by way of a specially crafted URL. This can be done through any medium that can contain URL web links that are controlled by the attacker, such as a link in an email, a link on a website, or a redirect on a website. In addition, compromised websites and websites 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 websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the affected website by way of a specially crafted URL.

What systems are primarily at risk from the vulnerability? 
System Center Configuration Manager servers with users who are authorized to access the System Center Configuration Manager Admin UI are primarily at risk.

What does the update do? 
This update modifies the way that System Center Configuration Manager handles specially crafted requests.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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.

Update Information

Security Central

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 website provides additional information about security in Microsoft products.

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

Affected Software

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

Microsoft Systems Management Server 2003 Service Pack 3

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 interventionFor Microsoft Systems Management Server 2003:
SMS2003-SP3-KB2733631-X86-ENU.exe /quiet
Installing without restartingFor Microsoft Systems Management Server 2003:
SMS2003-SP3-KB2733631-X86-ENU.exe /norestart
Update log fileKB2733631.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required?No, this security update does not require a restart.
HotPatchingNot applicable
Removal Information Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2733631$\Spuninst folder
File Information See Microsoft Knowledge Base Article 2733631
Registry Key Verification For Microsoft Systems Management Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Systems Management Server 2003\SP3\KB2733631

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, see Microsoft Knowledge Base Article 832475.

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
/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 :full 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/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:fullpath 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.

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 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 System Center Configuration Manager 2007 Service Pack 2

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 interventionFor Microsoft System Center Configuration Manager 2007:
msiexec.exe /i SCCM2007-SP2-KB2721642-V2-ENU.msi /quiet /L*v KB2721642.log
Installing without restartingFor Microsoft System Center Configuration Manager 2007:
msiexec.exe /i SCCM2007-SP2-KB2721642-V2-ENU.msi /norestart /L*v KB2721642.log
Update log fileKB2721642.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required?No, this security update does not require a restart.
HotPatchingNot applicable
Removal Information Use the Installed Updates window as build-in Administrator or run msiexec from an elevated command line.
File Information See Microsoft Knowledge Base Article 2721642
Registry Key Verification For Microsoft System Center Configuration Manager 2007:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\System Center Configuration Manager 2007\SP2\KB2721642

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section.

This security update requires that Windows Installer 3.1 or later version be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:

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
/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 or /q[n|b|r|f]Quiet mode, no user interaction or
/q[n|b|r|f] sets user interface level:
n - No user interface
b - Basic user interface
r - Reduced user interface
f - Full user interface (default)
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.
/ promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/l[ i|w|e|a|r|u|c|m|o|p|v|x |+|!|*] < LogFile > Enables logging. Options:
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log< LogFile > Equivalent of /l* <LogFile>.

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
SwitchDescription
/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.
/ promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/l[ i|w|e|a|r|u|c|m|o|p|v|x |+|!|*] < LogFile > Enables logging. Options:
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/ 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 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 that this security update is installed by reviewing the registry key listed in the Reference Table in this section.

Other Information

Acknowledgments

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

  • Andy Yang of Stratsec for reporting the Reflected XSS Vulnerability (CVE-2012-2536)

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 go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

How to obtain help and support for this security update

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 (September 11, 2012): Bulletin published.
  • V1.1 (September 12, 2012): Removed Microsoft System Center Configuration Manager 2007 R2 and Microsoft System Center Configuration Manager 2007 R3 from the Non-Affected Software table and added a bulletin FAQ that addresses the issue. Also added a bulletin FAQ to address the server roles that require this update. These are bulletin changes only. There were no changes to detection logic or security update files.
  • V1.2 (November 13, 2012): Revised bulletin to rerelease the KB2721642 update for System Center Configuration Manager 2007. Customers who have successfully installed only the KB2721642 EN (English) version of the update do not need to take any action.

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

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