-->
Security Bulletin
Vulnerabilities in Lync Could Allow Remote Code Execution (2707956)
Published: June 12, 2012
Sep 19, 2018 Before you install the Microsoft Communicator for Mac 2011 13.1 Update, make sure that the computer is running Microsoft Communicator for Mac 2011 and Mac OS X v10.5.8 or a later version of the Mac OS X operating system. To verify that the computer meets this prerequisite, click About This Mac on the Apple menu. How to obtain the update. Aug 04, 2015 There are two options for setting up Microsoft Office Communicator on your local computer: 1. You can use the setup script, or 2. You can configure the client manually. Using the setup script (recommended) To set up the client using the setup script: Download and run the.reg file. You can find the file by navigating to HostPilot Services. Communicator for Mac is a client that allows you to communicate withothers via instant messaging, PC-to-PC phone calls, and videoconferences; you can also see others' availability and sharedocuments. Communicator for Mac is the counterpart to the Windowsclient Office Communicator.It is part of Office 2011, andits capabilities are closely integrated with other Officeapplications.
Version: 1.0
General Information
This security update resolves one publicly disclosed vulnerability and three privately reported vulnerabilities in Microsoft Lync. The most severe vulnerabilities could allow remote code execution if a user views shared content that contains specially crafted TrueType fonts.
This security update is rated Important for Microsoft Lync 2010, Microsoft Lync 2010 Attendee, Microsoft Lync 2010 Attendant (32-bit), and Microsoft Lync 2010 Attendant (64-bit). For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by correcting how specially crafted True Type Font files are handled, correcting the manner in which Microsoft Lync loads external libraries, and modifying the way that SafeHTML function sanitizes HTML content. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically 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 from Microsoft Update and install this update manually. For information about specific configuration options in automatic updating in supported editions of Windows XP and Windows Server 2003, see Microsoft Knowledge Base Article 294871. For information about automatic updating in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, see Understanding Windows automatic updating.
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 2707956 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
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
| Software | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|
| Microsoft Communicator 2007 R2 (KB2708980) | Information Disclosure | Important | None |
| Microsoft Lync 2010 (32-bit) (KB2693282) | Remote Code Execution | Important | None |
| Microsoft Lync 2010 (64-bit) (KB2693282) | Remote Code Execution | Important | None |
| Microsoft Lync 2010 Attendee (admin level install) (KB2696031) Microsoft Lync 2010 Attendee[1] (user level install) (KB2693283) | Remote Code Execution | Important | None |
| Microsoft Lync 2010 Attendant (32-bit) (KB2702444) | Remote Code Execution | Important | None |
| Microsoft Lync 2010 Attendant (64-bit) (KB2702444) | Remote Code Execution | Important | None |
| Affected Software | TrueType Font Parsing Vulnerability - CVE-2011-3402 | TrueType Font Parsing Vulnerability - CVE-2012-0159 | Lync Insecure Library Loading Vulnerability - CVE-2012-1849 | HTML Sanitization Vulnerability - CVE-2012-1858 | Aggregate Severity Rating | |
|---|---|---|---|---|---|---|
| Microsoft Communicator 2007 R2 | Not applicable | Not applicable | Not applicable | **Important** Information Disclosure | **Important** | |
| Microsoft Lync 2010 (32-bit) | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Information Disclosure | **Important** | |
| Microsoft Lync 2010 (64-bit) | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Information Disclosure | **Important** | |
| Microsoft Lync 2010 Attendee | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Remote Code Execution | **Important** Information Disclosure | **Important** | |
| Microsoft Lync 2010 Attendant (32-bit) | Not applicable | Not applicable | **Important** Remote Code Execution | Not applicable | **Important** | |
| Microsoft Lync 2010 Attendant (64-bit) | Not applicable | Not applicable | **Important** Remote Code Execution | Not applicable | **Important** | |
TrueType Font Parsing Vulnerability - CVE-2011-3402
A remote code execution vulnerability exists in the way that affected components handle shared content that contains specially crafted TrueType fonts. The vulnerability could allow remote code execution if a user views shared content that contains specially crafted TrueType fonts. 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. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-3402.
Mitigating Factors for TrueType Font Parsing Vulnerability - CVE-2011-3402
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 who successfully exploited this vulnerability could gain the same user rights as the current 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.
Workarounds for TrueType Font Parsing Vulnerability - CVE-2011-3402
Microsoft has not identified any workarounds for this vulnerability.
FAQ for TrueType Font Parsing Vulnerability - CVE-2011-3402
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when specially crafted True Type Font (TTF) files are incorrectly handled.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. If the current 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.
How could an attacker exploit the vulnerability?
An attacker could share content that contains specially crafted TrueType fonts. The vulnerability could be exploited when a user views the shared content that contains specially crafted TrueType fonts.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update addresses the vulnerability by correcting how specially crafted TTF files are handled.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2011-3402.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Although this vulnerability has previously been exploited through limited, targeted attacks, the exploited attack vectors were addressed in MS11-087, Vulnerability in Windows Kernel-Mode Drivers Could Allow Remote Code Execution (2639417). Microsoft had not received any information to indicate that the attack vectors addressed in this bulletin had been publicly used to attack customers when this security bulletin was originally issued.
TrueType Font Parsing Vulnerability - CVE-2012-0159
A remote code execution vulnerability exists in the way that affected components handle shared content that contains specially crafted TrueType fonts. The vulnerability could allow remote code execution if a user views shared content that contains specially crafted TrueType fonts. 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. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0159.
Mitigating Factors for TrueType Font Parsing Vulnerability - CVE-2012-0159
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 who successfully exploited this vulnerability could gain the same user rights as the current 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.
Workarounds for TrueType Font Parsing Vulnerability - CVE-2012-0159
Microsoft has not identified any workarounds for this vulnerability.
FAQ for TrueType Font Parsing Vulnerability - CVE-2012-0159
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when specially crafted True Type Font (TTF) files are incorrectly handled.
Microsoft Communicator Mac Uninstall
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. If the current 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.
How could an attacker exploit the vulnerability?
An attacker could share content that contains specially crafted TrueType fonts. The vulnerability could be exploited when a user views the shared content that contains specially crafted TrueType fonts.
What systems are primarily at risk from the vulnerability?
Workstations are primarily at risk for this vulnerability.
What does the update do?
The update addresses the vulnerability by correcting how specially crafted TTF files are handled.
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.
Lync Insecure Library Loading Vulnerability - CVE-2012-1849
A remote code execution vulnerability exists in the way that Microsoft Lync handles the loading of DLL 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. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1849.
Mitigating Factors for Lync Insecure Library Loading Vulnerability - CVE-2012-1849
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:
- For an attack to be successful, a user must visit an untrusted remote file system location or WebDAV share and open a legitimate file (such as an .ocsmeet file) from this location that is then loaded by a vulnerable application.
- The file sharing protocol, Server Message Block (SMB), is often disabled on the perimeter firewall. This limits the potential attack vectors for this vulnerability.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on 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.
Workarounds for Lync Insecure Library Loading Vulnerability - CVE-2012-1849
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:
Disable loading of libraries from WebDAV and remote network shares
Note See Microsoft Knowledge Base Article 2264107 to deploy a workaround tool that allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.
Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue.
Note See Microsoft Knowledge Base Article 2264107 to use the automated Microsoft Fix it solution to deploy the registry key to block the loading of libraries for SMB and WebDAV shares. Note that this Fix it solution does require you to install the workaround tool also described in Microsoft Knowledge Base Article 2264107 first. This Fix it solution only deploys the registry key and requires the workaround tool in order to be effective. We recommend that administrators review the KB article closely prior to deploying this Fix it solution.
Disable theWebClientservice
Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning (WebDAV) client service. After applying this workaround it is still possible for remote attackers who successfully exploit this vulnerability to cause the system to run programs located on the targeted user's computer or the Local Area Network (LAN), but users will be prompted for confirmation before opening arbitrary programs from the Internet.
To disable the WebClient Service, follow these steps:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Disabled. If the service is running, click Stop.
- Click OK and exit the management application.
Impact of workaround. When the WebClient service is disabled, Web Distributed Authoring and Versioning (WebDAV) requests are not transmitted. In addition, any services that explicitly depend on the Web Client service will not start, and an error message will be logged in the System log. For example, WebDAV shares will be inaccessible from the client computer.
How to undo the workaround.
To re-enable the WebClient Service, follow these steps:
- Click Start, click Run, type Services.msc and then click OK.
- Right-click WebClient service and select Properties.
- Change the Startup type to Automatic. If the service is not running, click Start.
- Click OK and exit the management application.
Block TCP ports 139 and 445 at the firewall
These ports are used to initiate a connection with the affected component. Blocking TCP ports 139 and 445 at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.
Impact of workaround. Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below:
- Applications that use SMB (CIFS)
- Applications that use mailslots or named pipes (RPC over SMB)
- Server (File and Print Sharing)
- Group Policy
- Net Logon
- Distributed File System (DFS)
- Terminal Server Licensing
- Print Spooler
- Computer Browser
- Remote Procedure Call Locator
- Fax Service
- Indexing Service
- Performance Logs and Alerts
- Systems Management Server
- License Logging Service
How to undo the workaround. Unblock TCP ports 139 and 445 at the firewall. For more information about ports, see TCP and UDP Port Assignments.
FAQ for Lync Insecure Library Loading Vulnerability - CVE-2012-1849
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when Microsoft Lync incorrectly restricts the path used for loading external libraries.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the current user. If the current 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.
How could an attacker exploit the vulnerability?
An attacker could convince a user to open a legitimate Microsoft Lync related file (such as an .ocsmeet file) that is located in the same network directory as a specially crafted dynamic link library (DLL) file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In an email attack scenario, an attacker could exploit the vulnerability by sending a legitimate Microsoft Lync-related file (such as an .ocsmeet file) to a user, and convincing the user to place the attachment into a directory that contains a specially crafted DLL file and to open the legitimate file. Then, while opening the legitimate file, Microsoft Lync could attempt to load the DLL file and execute any code it contained.
In a network attack scenario, an attacker could place a legitimate Microsoft Lync-related file and a specially crafted DLL in a network share, a UNC, or WebDAV location and then convince the user to open the file.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Lync is used, including workstations and terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update addresses this vulnerability by correcting how Microsoft Lync loads external libraries.
Is this vulnerability related to Microsoft Security Advisory 2269637?Yes, this vulnerability is related to the class of vulnerabilities, described in Microsoft Security Advisory 2269637, that affects how applications load external libraries.
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.
HTML Sanitization Vulnerability - CVE-2012-1858
An information disclosure vulnerability exists in the way that HTML is filtered that could allow an attacker to perform cross-site scripting attacks and run script in the security context of the current user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1858.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2012-1858
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds for HTML Sanitization Vulnerability - CVE-2012-1858
Microsoft has not identified any workarounds for this vulnerability.
FAQ for HTML Sanitization Vulnerability - CVE-2012-1858
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited the vulnerability could perform cross-site scripting attacks against Lync or Microsoft Communicator users. An attacker could then potentially run script on behalf of a victim user.
What causes the vulnerability?
The vulnerability is caused by the way that SafeHTML sanitizes HTML.
Is this vulnerability related to CVE-2012-1858 in MS12-037,Cumulative Security Update for Internet Explorer?
Yes, the HTML Sanitization Vulnerability, CVE-2012-1858, also affects Internet Explorer.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited the vulnerability could perform cross-site scripting attacks against Lync or Microsoft Communicator users. An attacker could then potentially run script on behalf of a victim user.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker must have the ability to submit a specially crafted script to a Lync or Microsoft Communicator chat window. Because of the vulnerability, in specific situations the specially crafted script is not properly sanitized, which subsequently could lead to an attacker-supplied script being run in the security context of a user who views the malicious content.
For cross-site scripting attacks, this vulnerability requires that a user receives a specially crafted chat message for any malicious action to occur.
What systems are primarily at risk from the vulnerability?
Systems where Lync or Microsoft Communicator are used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that SafeHTML sanitizes HTML content.
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
Detection and Deployment Tools and Guidance
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 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.'
For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see Check for software updates automatically.
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.
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 |
|---|---|
| Microsoft Communicator 2007 R2 | Yes |
| Microsoft Lync 2010 (32-bit) | Yes |
| Microsoft Lync 2010 (64-bit) | Yes |
| Microsoft Lync 2010 Attendee (admin level install) | Yes |
| Microsoft Lync 2010 Attendee (user level install) | No |
| Microsoft Lync 2010 Attendant (32-bit) | Yes |
| Microsoft Lync 2010 Attendant (64-bit) | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
|---|---|---|
| Microsoft Communicator 2007 R2 | Yes | Yes |
| Microsoft Lync 2010 (32-bit) | Yes | Yes |
| Microsoft Lync 2010 (64-bit) | Yes | Yes |
| Microsoft Lync 2010 Attendee (admin level install) | Yes | Yes |
| Microsoft Lync 2010 Attendee (user level install) | No | No |
| Microsoft Lync 2010 Attendant (32-bit) | Yes | Yes |
| Microsoft Lync 2010 Attendant (64-bit) | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
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 uses WSUS 3.0 for detection of updates. For more information about System Center Configuration Manager Software Update Management, visit System Center.
For more information about SMS, visit the SMS website.
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 Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Communicator 2007 R2, Microsoft Lync 2010, Microsoft Lync 2010 Attendee, Microsoft Lync 2010 Attendant
Reference Table
Microsoft Communicator For Mac Download
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Microsoft Communicator
| 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 Lync 2007 R2 (KB2708980): communicator.msp /passive |
| For Microsoft Lync 2010 (32-bit) (KB2693282): lync.msp /passive | |
| For Microsoft Lync 2010 (64-bit) (KB2693282): lync.msp /passive | |
| For Microsoft Lync 2010 Attendee (admin level install) (KB2696031): attendeeadmin.msp /passive | |
| For Microsoft Lync 2010 Attendee (user level install) (KB2693283): attendeeuser.msp /passive | |
| For Microsoft Lync 2010 Attendant (32-bit) (KB2702444): attendantconsole.msp /passive | |
| For Microsoft Lync 2010 Attendant (64-bit) (KB2702444): attendantconsole.msp /passive | |
| Installing without restarting | For Microsoft Lync 2007 R2 (KB2708980): communicator.msp /norestart |
| For Microsoft Lync 2010 (32-bit) (KB2693282): lync.msp /norestart | |
| For Microsoft Lync 2010 (64-bit) (KB2693282): lync.msp /norestart | |
| For Microsoft Lync 2010 Attendee (admin level install) (KB2696031): attendeeadmin.msp /norestart | |
| For Microsoft Lync 2010 Attendee (user level install) (KB2693283): attendeeuser.msp /norestart | |
| For Microsoft Lync 2010 Attendant (32-bit) (KB2702444): attendantconsole.msp /norestart | |
| For Microsoft Lync 2010 Attendant (64-bit) (KB2702444): attendantconsole.msp /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, 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 item in Control Panel. |
| File Information | For Microsoft Lync 2007 R2: See Microsoft Knowledge Base Article 2708980 |
| For Microsoft Lync 2010: See Microsoft Knowledge Base Article 2693282 | |
| For Microsoft Lync 2010 Attendee (admin level install): See Microsoft Knowledge Base Article 2696031 For Microsoft Lync 2010 Attendee (user level install): See Microsoft Knowledge Base Article 2693283 | |
| For Microsoft Lync 2010 Attendant (32-bit and 64-bit): See Microsoft Knowledge Base Article 2702444 | |
| Registry Key Verification | Not applicable |
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| /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) |
| /passive | Unattended mode - progress bar only. |
| /norestart | Do not restart after the installation is complete. |
| /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>. |