MS09-056: Vulnerabilities in CryptoAPI could allow spoofing

Microsoft has released security bulletin MS09-056. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• Home users:
  http://www.microsoft.com/security/updates/bulletins/200910.aspx (http://www.microsoft.com/security/updates/bulletins/200910.aspx)
  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:
  http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/MS09-056.mspx (http://www.microsoft.com/technet/security/bulletin/MS09-056.mspx)

How to obtain help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site: North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site: For enterprise customers, support for security updates is available through your usual support contacts.

Known issues that affect this security update

Services that are required by Communications Server are not started after you install this update and then restart a computer that is running any of the following versions of Communications Server:

• Live Communications Server 2005 (LCS)
• Live Communications Server 2005 SP1
• Office Communications Server 2007 Enterprise edition (OCS)
• Office Communications Server 2007 Standard edition
• Office Communications Server 2007 R2 Enterprise edition
• Office Communications Server 2007 R2 Standard edition
• Office Communicator 2007 Evaluation version only*
• Office Communicator 2007 R2 Evaluation version only*
• Office Communicator 2005 Evaluation version only*

*The licensed production version of this application is not affected by this known issue. Only Office Communicator clients that are in their 180-day evaluation period are affected by this issue.

When this problem occurs, the following error events are logged in the Application logs in the Event Viewer of the affected servers:

• Live Communications Server 2005
  Event Type: Error
  Event Source: Live Communications Server
  Event Category: (1000)
  Event ID: 12290
  Date: Date
  Time: Time
  User: N/A
  Computer: Computer
  Description:
  The evaluation period for Microsoft Office Live Communication Server 2005 has expired. Obtain the released version of this product and upgrade to the non-evaluation version by running setup.exe.
• Office Communications Server 2007
  Log Name: Office Communications Server
  Source: OCS Server
  Date: Date
  Event ID: 12290
  Task Category: (1000)
  Level: Error
  Keywords: Classic
  User: N/A
  Computer: Computer
  Description:
  The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product.
  
  
  Log Name: Office Communications Server
  Source: OCS Server
  Date: Date
  Event ID: 12299
  Task Category: (1000)
  Level: Error
  Keywords: Classic
  User: N/A
  Computer: Computer
  Description:
  The service is shutting down due to an internal error.
  
  
  Error Code: C3E93C23 (SIPPROXY_E_INVALID_INSTALLATION_DATA)
  Cause: Check the previous entries in the event log for the failure reason.
  Resolution:
  Check the previous event log entries and resolve them. Restart the server. If the problem persists, contact Product Support Services.

When this problem occurs, the required services behave as if an expired trial version of the product is installed. This behavior affects the whole Communications Server enterprise that is hosted by the affected server or servers.

Customers who are not running OCS or LCS server are not affected by this known issue, and can safely ignore this issue.

Customers who have deployed the OCS or LCS product on a server should assess the risk that is involved to decide whether to install the security update on that server. These customers should revisit this Knowledge Base article often, because this article will be updated as soon as more information and a resolution are available.

Resolution for the known issue

A fix that resolves this issue is available for download from the Microsoft Download Center. To obtain the fix, visit the following Microsoft Web page: The fix (OCSASNFix.exe) is governed by the Microsoft Software License Agreement for Office Communications Server 2007 R2, Office Communications Server 2007, Live Communications Server 2005, Office Communicator 2007 R2, Office Communicator 2007, and Office Communicator 2005.

This fix works for both clients and servers, and it is applicable to the following roles for all versions of Office Communications Server and Live Communications Server 2005 SP1 and for evaluation versions of Office Communicator:

• Standard Edition Server
• Director server role
• Enterprise Edition Consolidated
• Enterprise Edition Distributed – Front End
• Edge Server
• Proxy server role
• Office Communicator 2007 Evaluation version only
• Office Communicator 2007 R2 Evaluation version only
• Office Communicator 2005 Evaluation version only

To run the fix, type the following command at a command prompt, and then press ENTER: When you run the command on a computer that is running Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005 Service Pack 1, you receive a message that resembles the following: When you run the command on a computer that is running an evaluation version of Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005, you receive a message that resembles the following: This fix can be applied either before or after you install security update 974571. If you apply the fix after you install security update 974571, we recommend that you apply the fix before you restart the computer. If you already restarted the computer after you installed security update 974571, this fix can still be applied. However, the Office Communication Services must be started manually.

If all services start without any issues, this indicates that this fix has been applied and is working correctly.

This fix sets the OCSASNFIX DWORD value to 1 for the following registry subkey on the OCS 2007/R2 and LCS 2005-SP1 Server:

Additional known issues with this security update

When you deploy the Standard Edition role on a new installation of any version of Office Communications Server, activation fails if security update 974571 is installed. To resolve this problem, apply this fix, and then run the activation again.

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

Windows 2000 file information

For all supported editions of Microsoft Windows 2000 Service Pack 4

Windows XP and Windows Server 2003 file information

• The files that apply to a specific service branch (QFE, GDR) are noted in the "Service branch" column.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
• In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed by using a Microsoft digital signature.

For all supported x86-based versions of Windows XP

For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition

For all supported x86-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

Windows Vista and Windows Server 2008 file information

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR
  6.0.6002.18xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	GDR
  6.0.6002.22xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	LDR

• Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

For all supported x86-based versions of Windows Vista and Windows Server 2008

For all supported x64-based versions of Windows Vista and Windows Server 2008

For all supported IA-64-based versions of Windows Server 2008

Windows 7 and Windows Server 2008 R2 file information

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2