An update for Commerce Server 2009 is available to fix a potential cross-site scripting (XSS) issue in Commerce Server 2009

Prerequisites

To apply this hotfix, you must have Microsoft Commerce Server 2009 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Post-installation steps

After you extract the hotfix package, you can obtain the following files and a source folder that has the Extensibility Kit and Default Site files:

• CommerceServer2007SP3-KB2423489-ENU.exe

• CS2009-KB2423489-x86.exe

• Hotfix.txt

• Extensibility Kit

  • Common\HttpModule\SecurePageModule.cs

  • UI\ProfilesSharePoint\Pages\CommerceLoginPage.aspx.cs

  • SharePointCommon\CrossSiteScriptingEncoder.cs

  • SharePointCommon\SharePointCommon.csproj

  • UI\Marketing\HttpHandlers\AdsRedir.ashx

  • Common\Controllers\MarketingController.cs

• Default Site

  • MicrosoftCommerceWSSDefaultSite.wsp\SiteTemplates\WSSCSDefaultSite\ writeReview.aspx

  • MicrosoftCommerceMOSSDefaultSite.WSP\SiteTemplates\MOSSCSDefaultSite\ writeReview.aspx

Note You must use the local administrator account when you install this hotfix, or you must run the hotfix by using the Run as Administrator option. If you are running Windows Vista, Windows Server 2008, or a later operating system, and if User Account Control (UAC) is enabled, we recommend that you use the Run as Administrator option.

After you run the installation files, use the method that is described for one of the following scenarios.

Scenario 1

If no sites are deployed, follow these steps:

1. Install the following hotfix installers:

   • CommerceServer2007SP3-KB2423489-ENU.exe

   • CS2009-KB2423489-x86.exe

2. Run the IISRESET command.

3. Run the SharePoint Commerce Services Configuration Wizard to deploy the new site by using the following updated files:

   • MicrosoftCommerceWebParts.WSP

   • MicrosoftCommerceWSSDefaultSite.WSP

   • MicrosoftCommerceMOSSDefaultSite.WSP

Scenario 2

If some sites are deployed, follow these steps:

1. Install the following hotfix installers:

   • CommerceServer2007SP3-KB2423489-ENU.exe

   • CS2009-KB2423489-x86.exe

2. Deploy the updated Web solution package (WSP) file by using the following stsadm command:

   stsadm -o upgradesolution -name microsoftcommercewebparts.wsp -filename MicrosoftCommerceWebParts.WSP -immediate -allowgacdeployment

3. Update the writeReview files that are located in the following folder in a typical installation of SharePoint 2007 and of Commerce Server 2009:

   • Microsoft Office SharePoint Server: <system drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\MOSSCSDefaultSite

   • Windows SharePoint Services: <system drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\WSSCSDefaultSite

4. Open SharePoint Designer, and on the File menu, click Open Site. In the Open Site dialog box, select the site that you want to change.

5. Highlight the file that is to be updated in <sitename>\pages\writeReview.aspx, right-click the file name, and then select Reset To Site Definition.

6. After the page that is in the content database is overwritten, click YES to continue.

7. The site displays the new file the next time that the page is loaded from the site. 
   
   Note If you do not follow the steps that are listed in Scenario2 to update the site, the site displays the old file when you reload it.

8. Run the IISRESET command.

Scenario 3

If Web Parts are customized by using the CommerceSharePointExtensibilityKit tool, follow these steps:

1. Install the following hotfix installers:

   • CommerceServer2007SP3-KB2423489-ENU.exe

   • CS2009-KB2423489-x86.exe

2. Locate the updated source files in the hotfix package:

   • SecurePageModulecs that is located in Common\HttpModule\SecurePageModule.cs

   • CommerceLoginPage.aspx.cs that is located in UI\ProfilesSharePoint\Pages\CommerceLoginPage.aspx.cs

   • SharepPointCommon. Csproj that is located in SharePointCommon\SharepointCommon\SharePointCommon.csproj

   • AdsRedir.ashx that is located in UI\Marketing\HttpHandlers\AdsRedir.ashx

   • MarketingController.cs that is located in Common\Controllers\MarketingController.cs

   • SiteContext.cs that is located in Common\SiteContext.cs

3. If you customized any of these files, you have to merge the highlighted changes in the hotfix copy of the files into the copy that is located in the CommerceSharePointExtensibilityKit folder.

4. Locate the updated source file in the CrossSiteScriptingEncoder.cs folder.

5. Compile the Web Parts assemblies.

6. If the custom site also uses the writeReview.aspx from Commerce Server 2009 default site, you have to follow the steps that are listed in Scenario 2 to change the writeReview.aspx files, and you have to reset to site definition by using SharePoint Designer.

Note The CommerceSharePointExtensibilityKit folder is located in the following path:

<system drive>\Program Files\Microsoft Commerce Server 2007\Microsoft Commerce Server 2009\Sdk\Samples\CommerceSharePointExtensibilityKit.zip

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.