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

Microsoft Security Bulletin MS13-054 - Critical

Vulnerability in GDI+ Could Allow Remote Code Execution

Published: July 09, 2013 | Updated: December 16, 2013

Version: 1.3

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft Windows, Microsoft Office, Microsoft Lync, and Microsoft Visual Studio. The vulnerability could allow remote code execution if a user views shared content that embeds TrueType font files.

This security update is rated Critical for all supported releases of Microsoft Windows and affected editions of Microsoft Lync 2010 and Microsoft Lync 2013. The security update is rated Important for affected releases of Microsoft Office and supported editions of Microsoft Visual Studio .NET 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting the way Microsoft Windows and affected software handle specially crafted TrueType Font (TTF) files. 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.  Most customers have automatic updating enabled and 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 and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately 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.

Knowledge Base Article

Knowledge Base Article2848295
File informationYes
SHA1/SHA2 hashesYes
Known issuesYes

Affected and Non-Affected Software

The following software has 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 

Operating SystemMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Windows XP
Windows XP Service Pack 3
(Windows GDI+)
(2834886)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 3
(Windows XP Tablet PC Edition 2005 only)
(Journal)
(2835364)
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCriticalNone
Windows Server 2003
Windows Server 2003 Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCriticalNone
Windows Server 2003 with SP2 for Itanium-based Systems
(Windows GDI+)
(2834886)
Remote Code ExecutionCriticalNone
Windows Vista
Windows Vista Service Pack 2
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Vista Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Vista Service Pack 2
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Vista x64 Edition Service Pack 2
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Vista x64 Edition Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Vista x64 Edition Service Pack 2
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Server 2008 for 32-bit Systems Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2008 for 32-bit Systems Service Pack 2
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Server 2008 for x64-based Systems Service Pack 2
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Server 2008 for x64-based Systems Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2008 for x64-based Systems Service Pack 2
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Server 2008 for Itanium-based Systems Service Pack 2
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows 7
Windows 7 for 32-bit Systems Service Pack 1
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows 7 for 32-bit Systems Service Pack 1
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows 7 for 32-bit Systems Service Pack 1
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows 7 for x64-based Systems Service Pack 1
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows 7 for x64-based Systems Service Pack 1
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows 7 for x64-based Systems Service Pack 1
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(Journal)
(2835364)
Remote Code ExecutionCritical2660649 in MS12-034
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(DirectWrite)
(2835361)
Remote Code ExecutionCritical2658846 in MS12-034
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows 8
Windows 8 for 32-bit Systems
(DirectWrite)
(2835361)
Remote Code ExecutionCriticalNone
Windows 8 for 32-bit Systems
(Journal)
(2835364)
Remote Code ExecutionCriticalNone
Windows 8 for 64-bit Systems
(DirectWrite)
(2835361)
Remote Code ExecutionCriticalNone
Windows 8 for 64-bit Systems
(Journal)
(2835364)
Remote Code ExecutionCriticalNone
Windows Server 2012
Windows Server 2012
(DirectWrite)
(2835361)
Remote Code ExecutionCriticalNone
Windows Server 2012
(Journal)
(2835364)
Remote Code ExecutionCriticalNone
Windows RT
Windows RT[1]
(DirectWrite)
(2835361)
Remote Code ExecutionCriticalNone
Windows RT[1]
(Journal)
(2835364)
Remote Code ExecutionCriticalNone
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(Windows GDI+)
(2834886)
Remote Code ExecutionCritical2659262 in MS12-034
Windows Server 2012 (Server Core installation)
(DirectWrite)
(2835361)
Remote Code ExecutionCriticalNone

[1]Windows RT security updates are provided via Windows Update.

Microsoft Office

Office SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Office 2003 Service Pack 3
(2817480)
Remote Code ExecutionImportant2598253in MS12-034
Microsoft Office 2007 Service Pack 3
(2687309)
Remote Code ExecutionImportant2596672 in MS12-034
Microsoft Office 2010 Service Pack 1
(32-bit editions)
(2687276)
Remote Code ExecutionImportant2589337 in MS12-034
Microsoft Office 2010 Service Pack 1
(64-bit editions) (2687276)
Remote Code ExecutionImportant2589337 in MS12-034

Microsoft Developer Tools and Software

SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Visual Studio .NET 2003 Service Pack 1[1]
(2856545)
Remote Code ExecutionImportant971022 in MS09-062

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

Microsoft Communications Platforms and Software

SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Lync 2010 (32-bit)
(2843160)
Remote Code ExecutionCritical2827750 in MS13-041
Microsoft Lync 2010 (64-bit)
(2843160)
Remote Code ExecutionCritical2827750 in MS13-041
Microsoft Lync 2010 Attendee[1]
(user level install)
(2843162)
Remote Code ExecutionCritical2827751 in MS13-041
Microsoft Lync 2010 Attendee
(admin level install)
(2843163)
Remote Code ExecutionCritical2827752 in MS13-041
Microsoft Lync 2013 (32-bit)
(2817465)
Remote Code ExecutionCriticalNone
Microsoft Lync Basic 2013 (32-bit)
(2817465)
Remote Code ExecutionCriticalNone
Microsoft Lync 2013 (64-bit)
(2817465)
Remote Code ExecutionCriticalNone
Microsoft Lync Basic 2013
(64-bit)
(2817465)
Remote Code ExecutionCriticalNone

[1]This update is available from the Microsoft Download Center only. See the Update FAQ section for more information.

Non-Affected Software

Microsoft Office
Microsoft Office 2013 (32-bit editions)
Microsoft Office 2013 (64-bit editions)
Microsoft Office 2013 RT
Microsoft Developer Tools and Software
Microsoft Visual Studio 2005 Service Pack 1
Microsoft Visual Studio 2008 Service Pack 1
Microsoft Visual Studio 2010 Service Pack 1
Microsoft Visual Studio LightSwitch 2011
Microsoft Visual Studio 2012
Microsoft Visual Studio Team Foundation Server 2012
Microsoft Communications Platforms and Software
Microsoft Speech Server 2004
Microsoft Speech Server 2004 R2
Microsoft Live Meeting 2007 Console
Microsoft Live Communications Server 2003
Microsoft Live Communications Server 2005 Service Pack 1
Microsoft Communicator 2005
Microsoft Communicator 2005 Web Access
Microsoft Communicator 2007
Microsoft Communicator 2007 R2
Microsoft Communicator 2007 Web Access
Microsoft Communications Server 2007
Microsoft Communications Server 2007 Speech Server
Microsoft Communications Server 2007 R2
Microsoft Communicator 2007 R2 Attendant
Microsoft Communicator 2007 R2 Group Chat Admin
Microsoft Communicator 2007 R2 Group Chat Client
Microsoft Communicator for Mac 2011
Microsoft Lync for Mac 2011
Microsoft Lync 2010 Attendant (32-bit)
Microsoft Lync 2010 Attendant (64-bit)
Microsoft Lync Server 2010
Microsoft Lync Web Access 2013

CVE-2013-3129 is described in multiple security bulletins. How are these bulletins related? 
The TrueType Font Parsing Vulnerability (CVE-2013-3129) affects the following products:

  • Microsoft Windows components (MS13-054)
  • Microsoft Office (MS13-054)
  • Microsoft Lync (MS13-054)
  • Microsoft Visual Studio (MS13-054)
  • Microsoft Windows Kernel-Mode Driver (MS13-053)
  • Microsoft .NET Framework (MS13-052)
  • Microsoft Silverlight (MS13-052)

You need to install only the updates that correspond to the software you have installed on your system. If you need to install more than one of these updates, they can be installed in any sequence.

There are multiple update packages available for some supported releases of Microsoft Windows. Do I need to install all the updates that are listed in the Affected Software table for my system? 
Yes. Customers should apply all updates offered for the software installed on their systems.

Do I need to install these security updates in a particular sequence? 
No. Multiple updates for one version of Microsoft Windows can be applied in any sequence.

I am running one of the operating systems that is listed in the affected software table. Why am I not being offered the DirectWrite update? 
The update will only be offered to systems on which the affected component (DirectWrite) is installed.

Note On Windows Vista Service Pack 2, DirectWrite is not installed by default. On this operating system, DirectWrite is installed as part of any of the following updates: Windows Graphics, Imaging, and XPS Library (KB971512), Platform Update Supplement (KB2117917), or the Update for DirectWrite and XPS (KB2505189). Note that these updates are offered through automatic updating.

Note On Windows Server 2008 Service Pack 2, DirectWrite is not installed by default. The update for DirectWrite only applies if any one of the following updates is installed: Windows Graphics, Imaging, and XPS Library (KB971512), Platform Update Supplement (KB2117917), or the Update for DirectWrite and XPS (KB2505189). Note that these updates are offered through automatic updating.

Note On supported editions of Windows Server 2008 R2, DirectWrite is not installed by default. On this operating system, the update for DirectWrite only applies if the Ink and Handwriting Services feature is enabled.

I am running one of the operating systems that is listed in the affected software table. Why am I not being offered the Journal update? 
The update will only be offered to systems on which the affected component (Journal) is installed.

Note On supported editions of Windows Server 2008,  Journal is not installed by default. On this operating system, the update for Journal only applies if Desktop Experience feature is enabled.

Note On supported editions of Windows Server 2008 R2 the update for Journal only applies if the Ink and Handwriting Services feature is enabled.

Note On supported editions of Windows Server 2012 the update for Journal only applies if the Ink and Handwriting Services feature is enabled.

I am running Microsoft Office 2010, which is listed as affected software. Why am I not being offered the 2687276 update?
The 2687276 update will only be offered to systems that are running Microsoft Office 2010 on supported editions of Windows XP or Windows Server 2003. The update is not applicable to other supported configurations because the vulnerable code is not present.

I am being offered this update for software that is not specifically listed in the Affected Software table. Why am I being offered this update? 
When updates address vulnerable code that exists in a component that is shared between multiple Microsoft Office products, the update is considered to be applicable to all products that contain the vulnerable component.

For example, when an update applies to Microsoft Office 2007 products only Microsoft Office 2007 may be specifically listed in the Affected Software table. However, the update could apply to Microsoft Word 2007, Microsoft Excel 2007, Microsoft Visio 2007, Microsoft Compatibility Pack, Microsoft Excel Viewer, or any other Microsoft Office 2007 product that is not specifically listed in the Affected Software table.

For example, when an update applies to Microsoft Office 2010 products, only Microsoft Office 2010 may be specifically listed in the Affected Software table. However, the update could apply to Microsoft Word 2010, Microsoft Excel 2010, Microsoft Visio 2010, Microsoft Visio Viewer, or any other Microsoft Office 2010 product that is not specifically listed in the Affected Software table.

For a list of Microsoft Office products an update may apply to, refer to the Microsoft Knowledge Base Article associated with the specific update.

In some cases due to the vulnerable code existing in a shared component of Office, an update may apply to Office products that are specifically listed in the Non-Affected Software table. For example, you may be offered a Microsoft Office security update even though this security bulletin indicates that the Office products that you do have installed are not affected. For more information on this behavior and recommended actions, see Microsoft Knowledge Base Article 830335.

Does the offer to update a non-vulnerable version of Microsoft Office software constitute an issue in the servicing model for Microsoft Office updates? 
No. The servicing model is based on how the update applies to shared components of Microsoft Office software. Some of the products that include the vulnerable component may not access the vulnerable code, and thus the software is not affected by the vulnerability. However, since the vulnerable code is present, the update is still considered applicable for the software.

The update mechanism is functioning correctly in that it detects a product version for applicable software on the system that is within the range of product versions that the update applies to, and thus offers the update. This helps to maintain consistency for shared files across Office products.

Why is the Lync 2010 Attendee (user level install) update only available from the Microsoft Download Center? 
Microsoft is releasing the update for Lync 2010 Attendee (user level install) to the Microsoft Download Center only. Because the user level installation of Lync 2010 Attendee is handled through a Lync session, distribution methods such as automatic updating are not appropriate for this type of installation scenario.

I do not have Microsoft Lync 2013 software installed. Why am I being offered an update for Microsoft Lync 2013? 
You may be offered an update for Microsoft Lync 2013 even though you do not have the affected software installed, if you have Microsoft Office software that contains the vulnerable shared component of Microsoft Office 2013 and Microsoft Lync 2013. Note that because the software does not access the vulnerable code, the software is not affected by the vulnerability. However, since the vulnerable code is present, this update will be offered.

Does the offer to update a non-vulnerable version of Microsoft Office software constitute an issue in the Microsoft update mechanism? 
No. The servicing model is based on how the update applies to shared components of Microsoft Office software. Some of the products that include the vulnerable component may not access the vulnerable code, and thus the software is not affected by the vulnerability. However, since the vulnerable code is present, the update is still considered applicable for the software.

The update mechanism is functioning correctly in that it detects a product version for applicable software on the system that is within the range of product versions that the update applies to, and thus offers the update. This helps to maintain consistency for shared files across Office products.

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareTrueType Font Parsing Vulnerability - CVE-2013-3129Aggregate Severity Rating
Windows XP
Windows XP Service Pack 3
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows XP Service Pack 3
(Microsoft Windows XP Tablet PC Edition 2005 only)
(Journal)
Critical
Remote Code Execution
Critical
Windows XP Professional x64 Edition Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2003
Windows Server 2003 Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2003 x64 Edition Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2003 with SP2 for Itanium-based Systems
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Vista
Windows Vista Service Pack 2
(DirectWrite)
(2835361)
Critical
Remote Code Execution
Critical
Windows Vista Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Vista Service Pack 2
(Journal)
Critical
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 2
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 2
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems Service Pack 2
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems Service Pack 2
(Windows GDI+)
(2834886)
Critical
Remote Code Execution
Critical
Windows 7
Windows 7 for 32-bit Systems Service Pack 1
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows 7 for 32-bit Systems Service Pack 1
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows 7 for 32-bit Systems Service Pack 1
(Journal)
Critical
Remote Code Execution
Critical
Windows 7 for x64-based Systems Service Pack 1
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows 7 for x64-based Systems Service Pack 1
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows 7 for x64-based Systems Service Pack 1
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows 8
Windows 8 for 32-bit Systems
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows 8 for 32-bit Systems
(Journal)
Critical
Remote Code Execution
Critical
Windows 8 for 64-bit Systems
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows 8 for 64-bit Systems
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2012
Windows Server 2012
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows Server 2012
(Journal)
Critical
Remote Code Execution
Critical
Windows RT
Windows RT[1]
(DirectWrite)
Critical
Remote Code Execution
Critical
Windows RT[1]
(Journal)
Critical
Remote Code Execution
Critical
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(Windows GDI+)
Critical
Remote Code Execution
Critical
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(Journal)
Critical
Remote Code Execution
Critical
Windows Server 2012 (Server Core installation)
(DirectWrite)
Critical
Remote Code Execution
Critical
Microsoft Office
Microsoft Office 2003 Service Pack 3Important
Remote Code Execution
Important
Microsoft Office 2007 Service Pack 3Important
Remote Code Execution
Important
Microsoft Office 2010 Service Pack 1
(32-bit editions)
Important
Remote Code Execution
Important
Microsoft Office 2010 Service Pack 1
(64-bit editions)
Important
Remote Code Execution
Important
Microsoft Developer Tools and Software
Microsoft Visual Studio .NET 2003 Service Pack 1Important
Remote Code Execution
Important
Microsoft Communications Platforms and Software
Microsoft Lync 2010 (32-bit)Critical
Remote Code Execution
Critical
Microsoft Lync 2010
(64-bit)
Critical
Remote Code Execution
Critical
Microsoft Lync 2010 Attendee
(user level install)
Critical
Remote Code Execution
Critical
Microsoft Lync 2010 Attendee
(admin level install)
Critical
Remote Code Execution
Critical
Microsoft Lync 2013 (32-bit)Critical
Remote Code Execution
Critical
Microsoft Lync Basic 2013 (32-bit)Critical
Remote Code Execution
Critical
Microsoft Lync 2013 (64-bit)Critical
Remote Code Execution
Critical
Microsoft Lync Basic 2013
(64-bit)
Critical
Remote Code Execution
Critical

A remote code execution vulnerability exists in the way that affected Windows components and other affected software handle specially crafted TrueType font files. The vulnerability could allow remote code execution if a user views shared content that embeds TrueType font 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 administrative rights.

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

Mitigating Factors

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 browsing 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.
  • By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML email messages in the Restricted sites zone, which disables font download by default. If a user clicks a link in an email message, the user could still be vulnerable to exploitation of this vulnerability through the web-based attack scenario. The vulnerability could also be exploited if a user opens an attachment that is sent in an email message.
  • The malicious file could be sent as an email attachment, but the attacker would have to convince the user to open the attachment in order to exploit the vulnerability.

Workarounds

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 the WebClient service

    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:

    1. Click Start, click Run, type Services.msc and then click OK.
    2. Right-click WebClient service and select Properties.
    3. Change the Startup type to Disabled. If the service is running, click Stop.
    4. 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:

    1. Click Start, click Run, type Services.msc and then click OK.
    2. Right-click WebClient service and select Properties.
    3. Change the Startup type to Automatic. If the service is not running, click Start.
    4. 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.

  • Disable the Preview Pane and Details Pane in Windows Explorer

    Disabling the Preview and Details panes in Windows Explorer prevents TrueType fonts from being viewed in Windows Explorer. While this prevents malicious files from being viewed in Windows Explorer, it does not prevent a local, authenticated user from running a specially crafted program to exploit this vulnerability.

    To disable these panes in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, perform the following steps:

    1. Open Windows Explorer, click Organize, and then click Layout.
    2. Clear both the Details pane and Preview pane menu options.
    3. Open Windows Explorer, click Organize, and then click Folder and search options.
    4. Click on the View tab
    5. Check the box for Always show icons, never thumbnails under Advanced settings.
    6. Close all open instances of Windows Explorer for the change to take effect.

    How to undo the workaround. To re-enable the Windows Explorer Preview and Details panes in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2:

    1. Open Windows Explorer, click Organize, and then click Layout.
    2. Select both the Details pane and Preview pane menu options.
    3. Open Windows Explorer, click Organize, and then click Folder and search options.
    4. Click on the View tab
    5. Clear the box for Always show icons, never thumbnails under Advanced settings.
    6. Close all open instances of Windows Explorer for the change to take effect.

FAQ

What is the scope of the vulnerability? 
This is a remote code execution vulnerability.

What causes the vulnerability? 
The vulnerability is caused when Windows, Office, Visual Studio, or Lync fails to properly handle specially crafted TrueType Fonts (TTF) files.

What is TrueType? 
TrueType is a digital font technology used in Microsoft operating systems.

What is GDI+? 
GDI+ is a graphics device interface that provides two-dimensional vector graphics, imaging, and typography to applications and programmers.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited the vulnerability through Windows GDI+ and Windows components could run arbitrary code in kernel mode and take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

An attacker who successfully exploited the vulnerability through Microsoft Office, Microsoft Visual Studio, or Microsoft Lync could gain the same user rights as the current user. If a 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? 
There are multiple means that could allow an attacker to exploit this vulnerability.

In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit this vulnerability and then convince a user to view the website. An attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by opening an attachment sent through email.

In a file sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit this vulnerability, and then convince a user to open the document file.

In a local attack scenario, an attacker could also exploit this vulnerability by running a specially crafted application to take complete control over the affected system. However, the attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability in this scenario.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk.

What does the update do? 
The update addresses the vulnerability by correcting the way Windows handles specially crafted TrueType Font (TTF) files.

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

Several resources are available to help administrators deploy security updates. 

  • Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and common security misconfigurations. 
  • Windows Server Update Services (WSUS), Systems Management Server (SMS), and System Center Configuration Manager (SCCM) help administrators distribute security updates. 
  • The Update Compatibility Evaluator components included with Application Compatibility Toolkit aid in streamlining the testing and validation of Windows updates against installed applications. 

For information about these and other tools that are available, see Security Tools for IT Pros

Affected Software

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

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file namesFor Windows XP Service Pack 3:
WindowsXP-KB2834886-x86-ENU.exe
For Windows XP Service Pack 3 (Windows XP Tablet PC Edition 2005 only):
WindowsXP-KB2835364-x86-ENU.exe
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB2834886-x64-ENU.exe
Installation switchesSee Microsoft Knowledge Base Article 262841
Update log fileKB2834886.log
KB2835364.log
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationFor all supported 32-bit editions of Windows XP and all supported x64-based editions of Windows XP:
Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2834886$\Spuninst folder
For Windows XP Service Pack 3 (Windows XP Tablet PC Edition 2005 only):
Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2835364$\Spuninst folder
File informationSee Microsoft Knowledge Base Article 2834886
See Microsoft Knowledge Base Article 2835364
Registry key verificationFor all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2834886\Filelist
For Windows XP Service Pack 3 (Windows XP Tablet PC Edition 2005 only):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2835364\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2834886\Filelist

Note The update for supported versions of Windows XP Professional x64 Edition also applies to supported versions of Windows Server 2003 x64 Edition.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file namesFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB2834886-x86-ENU.exe
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2834886-x64-ENU.exe
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2834886-ia64-ENU.exe
Installation switchesSee Microsoft Knowledge Base Article 262841
Update log fileKB2834886.log
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationUse Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2834886$\Spuninst folder
File informationSee Microsoft Knowledge Base Article 2834886
Registry key verificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2834886\Filelist

Note The update for supported versions of Windows Server 2003 x64 Edition also applies to supported versions of Windows XP Professional x64 Edition.

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file namesFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB2835361-x86.msu
Windows6.0-KB2834886-x86.msu
Windows6.0-KB2835364-x86.msu
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2835361-x64.msu
Windows6.0-KB2834886-x64.msu
Windows6.0-KB2835364-x64
msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2834886
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows Server 2008 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file namesFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2835361-x86.msu
Windows6.0-KB2834886-x86.msu
Windows6.0-KB2835364-x86.msu
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2835361-x64.msu
Windows6.0-KB2834886-x64.msu
Windows6.0-KB2835364-x64
.msu
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2834886-ia64.msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2834886
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows 7 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor all supported 32-bit editions of Windows 7:
Windows6.1-KB2835361-x86.msu
Windows6.1-KB2834886-x86.msu
Windows6.1-KB2835364-x86.msu
For all supported x64-based editions of Windows 7:
Windows6.1-KB2835361-x64.msu
Windows6.1-KB2834886-x64.msu
Windows6.1-KB2835364-x64
.msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2834886
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows Server 2008 R2 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2835361-x64.msu
Windows6.1-KB2834886-x64.msu
Windows6.1-KB2835364-x64.msu
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2835361-ia64.msu
Windows6.1-KB2834886-xia
4.msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2834886
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows 8 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor all supported 32-bit editions of Windows 8:
Windows8-RT-KB2835361-x86.msu
Windows8-RT-KB2835364-x86.msu
For all supported 64-bit editions of Windows 8:
Windows8-RT-KB2835361-x64.msu
Windows8-RT-KB2835364-x64.msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows Server 2012 (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.

Security update file nameFor all supported editions of Windows Server 2012:
Windows8-RT-KB2835361-x64.msu
Windows8-RT-KB2835364-x64.msu
Installation switchesSee Microsoft Knowledge Base Article 934307
Restart requirementYes, you must restart your system after you apply this security update.
Removal informationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
File informationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2835364
Registry key verificationNote A registry key does not exist to validate the presence of this update.

Windows RT (all editions)

The following table contains the security update information for this software.

DeploymentThis update is available via Windows Update only.
Restart RequirementYes, you must restart your system after you apply this security update.
Removal InformationClick Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2835361
See Microsoft Knowledge Base Article 2835364

Microsoft Office 2003 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Office 2003 Service Pack 3:
office2003-kb2817480-fullfile-enu.exe
Installation switchesSee Microsoft Knowledge Base Article 197147
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item in Control Panel.

Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File informationSee Microsoft Knowledge Base Article 2817480
Registry key verificationNot applicable

Microsoft Office 2007 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor all supported editions of Microsoft Office 2007:
ogl2007-kb2687309-fullfile-x86-glb.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item in Control Panel.
File informationSee Microsoft Knowledge Base Article 2687309
Registry key verificationNot applicable

Microsoft Office 2010 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor all supported editions of Microsoft Office 2010 (32-bit editions):
ogl2010-kb2687276-fullfile-x86-glb.exe
For all supported editions of Microsoft Office 2010 (64-bit editions):
ogl2010-kb2687276-fullfile-x64-glb.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item in Control Panel.
File informationSee Microsoft Knowledge Base Article 2687276
Registry key verificationNot applicable

Microsoft Visual Studio .NET 2003 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Microsoft Visual Studio .NET 2003:
VS7.1sp1-KB2856545-X86.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal InformationUse Add or Remove Programs item in Control Panel.
File InformationSee Microsoft Knowledge Base Article 2856545
Registry Key VerificationFor Microsoft Visual Studio .NET 2003:
HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Visual Studio\7.1\M2856545
"Installed" = dword:1

Microsoft Lync 2010, Microsoft Lync 2010 Attendee, Microsoft Lync 2013, and Microsoft Lync Basic 2013

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Microsoft Lync 2010 (32-bit) (2843160):
lync.msp
 For Microsoft Lync 2010 (64-bit) (2843160):
lync.msp
For Microsoft Lync 2010 Attendee (user level install) (2843162):
AttendeeUser.msp
For Microsoft Lync 2010 Attendee (admin level install) (2843163):
AttendeeAdmin.msp
For Microsoft Lync 2013 (32-bit) and Microsoft Lync Basic 2013 (32-bit):
lyncloc2013-kb2817465-fullfile-x86-glb.exe
For Microsoft Lync 2013 (64-bit) and Microsoft Lync Basic 2013 (64-bit):
lyncloc2013-kb2817465-fullfile-x64-glb.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal InformationUse Add or Remove Programs item in Control Panel.
File InformationFor all supported editions of Microsoft Lync 2010:
See Microsoft Knowledge Base Article 2843160
For Microsoft Lync 2010 Attendee (user level install):
See Microsoft Knowledge Base Article 2843162
For Microsoft Lync 2010 Attendee (admin level install):
See Microsoft Knowledge Base Article 2843163
For all supported editions of Microsoft Lync 2013:
See Microsoft Knowledge Base Article 2768004
Registry Key VerificationFor Microsoft Lync 2010 (32-bit):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4392
For Microsoft Lync 2010 (64-bit):
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4392
For Microsoft Lync 2010 Attendee (admin level install):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\94E53390F8C13794999249B19E6CFE33\InstallProperties\DisplayVersion = 4.0.7577.4392
For Microsoft Lync 2010 Attendee (user level install):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4392
For Microsoft Lync 2013 (32-bit) and Microsoft Lync Basic 2013 (32-bit):
Not applicable
For Microsoft Lync 2013 (64-bit) and Microsoft Lync Basic 2013 (64-bit):
Not applicable

Other Information

Acknowledgments

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

  • Ling Chuan Lee and Lee Yee Chan of F13 Laboratory for reporting the TrueType Font Parsing Vulnerability (CVE-2013-3129)

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 (July 9, 2013): Bulletin published.
  • V.1.1 (August 1, 2013): Bulletin revised to announce a detection change in the 2687276 update for Microsoft Office 2010. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action. In addition, bulletin revised to add update FAQs to help clarify the configurations to which the updates for Microsoft Office may apply.
  • V1.2 (August 13, 2013): Bulletin revised to announce a detection change for the 2687276 update for Microsoft Office 2010. This detection change only affects non-English deployments. There were no changes to the security update files. Customers who have already successfully updated their systems do not need to take any action.
  • V1.3 (December 16, 2013): Revised bulletin to announce a detection change to correct an offering issue for Windows RT (2835361) and for Windows RT (2835364). This is a detection change only. There were no changes to the update files. Customers who have successfully installed the update do not need to take any action.

Built at 2014-04-16T02:39:51Z-07:00

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