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

Microsoft Security Bulletin MS13-096 - Critical

Vulnerability in Microsoft Graphics Component Could Allow Remote Code Execution

Published: December 10, 2013 | Updated: December 20, 2013

Version: 1.2

General Information

Executive Summary

This security update resolves a publicly disclosed vulnerability in Microsoft Windows, Microsoft Office, and Microsoft Lync. The vulnerability could allow remote code execution if a user views content that contains specially crafted TIFF files.

This security update is rated Critical for all supported editions of Windows Vista, Windows Server 2008, Microsoft Office 2003, Microsoft Office 2007, Microsoft Office 2010, Microsoft Office Compatibility Pack, and Microsoft Office viewers. It is rated Important for all supported editions of Microsoft Lync 2010 and Microsoft Lync 2013. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting the way the affected software handles TIFF 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.

This security update addresses the vulnerability first described in Microsoft Security Advisory 2896666.

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 Article2908005
File informationYes
SHA1/SHA2 hashesYes
Known issuesNone

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 Vista
Windows Vista Service Pack 2
(2901674)
Remote Code ExecutionCriticalNone
Windows Vista x64 Edition Service Pack 2
(2901674)
Remote Code ExecutionCriticalNone
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2
(2901674)
Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems Service Pack 2
(2901674)
Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems Service Pack 2
(2901674)
Remote Code ExecutionCriticalNone
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(2901674)
Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(2901674)
Remote Code ExecutionCriticalNone

Microsoft Office

Office SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Office 2003
Microsoft Office 2003 Service Pack 3
(2850047)
Remote Code ExecutionCritical2817480 in MS13-054
Microsoft Office 2007
Microsoft Office 2007 Service Pack 3[1]
(2817641)
Remote Code ExecutionCritical2687309 in MS13-054
Microsoft Office 2010
Microsoft Office 2010 Service Pack 1 (32-bit editions)
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054
Microsoft Office 2010 Service Pack 2 (32-bit editions)
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054
Microsoft Office 2010 Service Pack 1 (64-bit editions)
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054
Microsoft Office 2010 Service Pack 2 (64-bit editions)
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054
Other Office Software
Microsoft Office Compatibility Pack Service Pack 3[1]
(2817641)
Remote Code ExecutionCritical2687309 in MS13-054
Microsoft Word Viewer[1]
(2850047)
Remote Code ExecutionCritical2817480 in MS13-054
Microsoft Excel Viewer[1]
(2817641)
Remote Code ExecutionCritical2687309 in MS13-054
Microsoft PowerPoint 2010 Viewer Service Pack 1[1]
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054
Microsoft PowerPoint 2010 Viewer Service Pack 2[1]
(2817670)
Remote Code ExecutionCritical2687276 in MS13-054

[1]The update for Microsoft Office 2003 also applies to Microsoft Word Viewer. The update for Microsoft Office 2007 also applies to Microsoft Office Compatibility Pack and to Microsoft Excel Viewer. The update for Microsoft Office 2010 also applies to Microsoft PowerPoint 2010 Viewer.

Microsoft Communications Platforms and Software

SoftwareMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Lync 2010
Microsoft Lync 2010 (32-bit)
(2899397)
Remote Code ExecutionImportant2843160 in MS13-054
Microsoft Lync 2010 (64-bit)
(2899397)
Remote Code ExecutionImportant2843160 in MS13-054
Microsoft Lync 2010 Attendee[1]
(user level install)
(2899393)
Remote Code ExecutionImportant2843162 in MS13-054
Microsoft Lync 2010 Attendee
(admin level install)
(2899395)
Remote Code ExecutionImportant2843163 in MS13-054
Microsoft Lync 2013
Microsoft Lync 2013 (32-bit)
(2850057)
Remote Code ExecutionImportant2817465 in MS13-054
Microsoft Lync Basic 2013 (32-bit)
(2850057)
Remote Code ExecutionImportant2817465 in MS13-054
Microsoft Lync 2013 (64-bit)
(2850057)
Remote Code ExecutionImportant2817465 in MS13-054
Microsoft Lync Basic 2013
(64-bit)
(2850057)
Remote Code ExecutionImportant2817465 in MS13-054

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

Non-Affected Software

Operating System
Windows XP Service Pack 3[1]
Windows XP Professional x64 Edition Service Pack 2[1]
Windows Server 2003 Service Pack 2[1]
Windows Server 2003 x64 Edition Service Pack 2[1]
Windows Server 2003 for Itanium-based Systems Service Pack 2[1]
Windows 7 for 32-bit Systems Service Pack 1[1]
Windows 7 for x64-based Systems Service Pack 1[1]
Windows Server 2008 R2 for x64-based Systems Service Pack 1[1]
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1[1]
Windows 8 for 32-bit Systems[1]
Windows 8 for x64-based Systems[1]
Windows 8.1 for 32-bit Systems[1]
Windows 8.1 for x64-based Systems[1]
Windows RT[1]
Windows RT 8.1[1]
Windows Server 2012[1]
Windows Server 2012 R2[1]
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)[1]
Windows Server 2012 (Server Core installation)[1]
Windows Server 2012 R2 (Server Core installation)[1]
Microsoft Office Suites and Software
Microsoft Office 2013 (32-bit editions)
Microsoft Office 2013 (64-bit editions)
Microsoft Office 2013 RT
Microsoft Communication 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 Server 2013
Microsoft Lync Web Access 2013

[1]These editions of Microsoft Windows are not affected if you do not have an affected version of Microsoft Office or Microsoft Lync installed on the platform.

If I applied the automated Microsoft Fix it solution previously described in Microsoft Security Advisory 2896666, should I undo the workaround after applying this update? 
Yes, customers should undo the workaround after applying this update. If you do not undo the workaround at some point, you will not be able to properly view TIFF files.

To undo the Microsoft Fix it solution, you can follow the steps in Microsoft Knowledge Base Article 2908005.

If I applied the Disable data collaboration in Lync workaround previously described in Microsoft Security Advisory 2896666, should I undo the workaround after applying this update? 
Yes, customers who have disabled collaboration in Lync should undo the workaround after applying the update. If you do not undo the workaround, you will not be able to share and collaborate on PowerPoint files, polls, and Whiteboard during Lync meetings.

To undo the Disable data collaboration in Lync workaround, see the Workarounds section in this bulletin.

Based on the configuration of my system, how do I know if my system is affected? 
Even if you are running an operating system that is not affected, your system could still be vulnerable if you have an affected version of Microsoft Office or Microsoft Lync installed. Refer to the following table to verify whether your system might be affected through a version of Office or Lync, and to verify the updates that are applicable to your configuration:

Affected SoftwareInstalled on Windows XP[1]Installed on Windows Server 2003 Service Pack 2Installed on Windows Vista Service Pack 2Installed on Windows Server 2008 Service Pack 2Installed on Windows 7 Service Pack 1Installed on Windows Server 2008 R2 Service Pack 1Installed on Windows 8Installed on Windows 8.1Installed on Windows Server 2012Installed on Windows Server 2012 R2
Microsoft Office 2003 Service Pack 3Affected
(Update 2850047)
Affected
(Update 2850047)
Affected
(Update 2850047 and Update 2901674)
Affected
(Update 2850047 and Update 2901674)
Affected
(Update 2850047)
Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]
Microsoft Office 2007 Service Pack 3Under active attack
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Microsoft Office 2010 Service Pack 1 (32-bit editions)Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2010 Service Pack 2 (32-bit editions)Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2010 Service Pack 1 (64-bit editions)Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2010 Service Pack 2 (64-bit editions)Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2013 (32-bit editions)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2013 (64-bit editions)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office 2013 RTNot applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Office Compatibility Pack Service Pack 3Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Microsoft Word ViewerAffected
(Update 2850047)
Affected
(Update 2850047)
Affected
(Update 2850047 and Update 2901674)
Affected
(Update 2850047 and Update 2901674)
Affected
(Update 2850047)
Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]
Microsoft Excel ViewerAffected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641 and Update 2901674)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Affected
(Update 2817641)
Microsoft PowerPoint 2010 Viewer Service Pack 1Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft PowerPoint 2010 Viewer Service Pack 2Affected
(Update 2817670)
Affected
(Update 2817670)
Affected
(Update 2901674)
Affected
(Update 2901674)
Not affectedNot affectedNot affectedNot affectedNot affectedNot affected
Microsoft Lync 2010 (32-bit)Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397 and Update 2901674)
Affected
(Update 2899397 and Update 2901674)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Microsoft Lync 2010 (64-bit)Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397 and Update 2901674)
Affected
(Update 2899397 and Update 2901674)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Affected
(Update 2899397)
Microsoft Lync 2010 Attendee (user level install)Affected
(Update 2899393)
Affected
(Update 2899393)
Affected
(Update 2899393 and Update 2901674)
Affected
(Update 2899393 and Update 2901674)
Affected
(Update 2899393)
Affected
(Update 2899393)
Affected
(Update 2899393)
Affected
(Update 2899393)
Affected
(Update 2899393)
Affected
(Update 2899393)
Microsoft Lync 2010 Attendee (admin level install)Affected
(Update 2899395)
Affected
(Update 2899395)
Affected
(Update 2899395 and Update 2901674)
Affected
(Update 2899395 and Update 2901674)
Affected
(Update 2899395)
Affected
(Update 2899395)
Affected
(Update 2899395)
Affected
(Update 2899395)
Affected
(Update 2899395)
Affected
(Update 2899395)
Microsoft Lync 2013 (32-bit)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Microsoft Lync Basic 2013 (32-bit)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Microsoft Lync 2013 (64-bit)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Microsoft Lync Basic 2013 (64-bit)Not applicable[2]Not applicable[2]Not applicable[2]Not applicable[2]Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)
Affected
(Update 2850057)

[1]Applies to Windows XP Service Pack 3 and Windows XP Professional x64 Edition Service Pack 2.

[2]Not a supported configuration for Microsoft Office or Microsoft Lync. 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.

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 or shared between multiple versions of the same Microsoft Office product, the update is considered to be applicable to all supported products and versions 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 more information on this behavior and recommended actions, see Microsoft Knowledge Base Article 830335. For a list of Microsoft Office products an update may apply to, refer to the Microsoft Knowledge Base Article associated with the specific update.

I am being offered this update for software that is not vulnerable. Why am I being offered this update? 
In some cases, an update may apply to Microsoft Office products that are specifically listed in the Non-Affected Software table or that are otherwise listed in the Affected Software table with "Not applicable" for security impact. For example, you may be offered a Microsoft Office security update even though this security bulletin indicates that the Office products or the version of the Office products that you do have installed are not affected. For more information on this behavior, see Microsoft Knowledge Base Article 830335.

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 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 offered an update may not access the vulnerable code, and thus the software is not affected by the vulnerability. However, 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 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 December bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareMicrosoft Graphics Component Memory Corruption Vulnerability - CVE-2013-3906Aggregate Severity Rating
Windows Vista
Windows Vista Service Pack 2 Critical
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 2Critical
Remote Code Execution
Critical
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2 Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2 Critical
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems Service Pack 2 Critical
Remote Code Execution
Critical
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2Critical
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems Service Pack 2Critical
Remote Code Execution
Critical
Microsoft Office
Microsoft Office 2003 Service Pack 3Critical
Remote Code Execution
Critical
Microsoft Office 2007 Service Pack 3Critical
Remote Code Execution
Critical
Microsoft Office 2010 Service Pack 1 (32-bit editions)Critical
Remote Code Execution
Critical
Microsoft Office 2010 Service Pack 1
(64-bit editions)
Critical
Remote Code Execution
Critical
Microsoft Office Compatibility Pack Service Pack 3Critical
Remote Code Execution
Critical
Microsoft Word ViewerCritical
Remote Code Execution
Critical
Microsoft Excel ViewerCritical
Remote Code Execution
Critical
Microsoft PowerPoint 2010 Viewer Service Pack 1Critical
Remote Code Execution
Critical
Microsoft PowerPoint 2010 Viewer Service Pack 2Critical
Remote Code Execution
Critical
Microsoft Lync
Microsoft Lync 2010 (32-bit)Important
Remote Code Execution
Important
Microsoft Lync 2010 (64-bit)Important
Remote Code Execution
Important
Microsoft Lync 2010 Attendee
(user level install)
Important
Remote Code Execution
Important
Microsoft Lync 2010 Attendee
(admin level install)
Important
Remote Code Execution
Important
Microsoft Lync 2013 (32-bit)Important
Remote Code Execution
Important
Microsoft Lync Basic 2013 (32-bit)Important
Remote Code Execution
Important
Microsoft Lync 2013 (64-bit)Important
Remote Code Execution
Important
Microsoft Lync Basic 2013
(64-bit)
Important
Remote Code Execution
Important

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

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:

  • 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

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 TIFF codec

    Note See Microsoft Knowledge Base Article 2908005 to use the automated Microsoft Fix it solution to enable or disable this workaround.

    Note This workaround is not applicable to Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT, and Windows RT 8.1.

    You can prevent TIFF files from being displayed by modifying the registry to control the parsing of the TIFF codec. By changing the registry entries, you can control which images are parsed and rendered and which images are rejected in GDI+. For example, you can select to parse and render Joint Photographic Experts Group (JPEG) images, but block Tagged Image File Format (TIFF) images.

    Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    Note After you change a registry entry, you must restart the application that uses the codec.

    To disable the TIFF codec:

    1. To add a registry entry, create one of the following registry subkeys for the appropriate Windows platform:

      For 32-bit systems:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Gdiplus

      For 32-bit applications on 64-bit systems:
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Gdiplus

      For 64-bit systems:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Gdiplus

    2. Create a DWORD value for the TIFF code by creating a registry entry (DWORD value) under the registry subkey you created in step 1:

      DisableTIFFCodec

    3. To disable the TIFF codec, set value of the DisableTIFFCodec registry entry to 1.

    Impact of Workaround. You will not be able to view TIFF files using any of the affected products.

    How to undo the workaround

    To re-enable the TIFF codec, set the value of the DisableTIFFCodec registry entry to 0.

  • Disable data collaboration in Lync

    Enterprise users who manage directly a Lync server can prevent PowerPoint files (which may be used as an attack vector to send specially crafted TIFF files) from being shared through Lync by using the Lync Server Control Panel to modify the Lync conferencing policy for data collaboration.

    For Lync 2010 and Lync 2013:

    1. Open the Lync Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.
    2. In the left navigation bar, click Conferencing and then click Conferencing Policy.
    3. In the list of conferencing policies, click Data collaboration, click Edit, and then click Show details.
    4. To prevent data collaboration, in Edit Conferencing Policy, click None. The default setting is Enable data collaboration.
    5. Click Commit.

    Impact of Workaround. Users will not be able to share and collaborate on PowerPoint files, polls, and Whiteboard during Lync meetings.

    How to undo the workaround

    To re-enable data collaboration:

    1. Open the Lync Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.
    2. In the left navigation bar, click Conferencing and then click Conferencing Policy.
    3. In the list of conferencing policies, click Data collaboration, click Edit, and then click Show details.
    4. To enable data collaboration, in Edit Conferencing Policy, click Enable data collaboration.
    5. Click Commit.

FAQ

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

What causes the vulnerability? 
The vulnerability is caused when Microsoft Windows, Microsoft Office, or Microsoft Lync fails to properly handle specially crafted TIFF files. System memory may be corrupted in such a way that an attacker could execute arbitrary code.

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

What is a TIFF file?
A TIFF (tagged image file format) file allows information to be embedded in the image file, such as the compression scheme, color mode, and size.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opens a specially crafted file or browses a website that contains specially crafted content. If the user is logged on with administrative user rights, 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.

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 an email attack scenario, an attacker could exploit the vulnerability by sending specially crafted Office data in the contents of an email message. The vulnerability could be exploited when a user opens or previews the specially crafted email message in Outlook while using Microsoft Word as the email reader. Note that by default, Microsoft Word is not the email reader in Outlook 2003. An attacker could also exploit the vulnerability by sending a specially crafted Office file to the user, and then convincing the user to open the file with an affected version of Microsoft Office software.

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 running affected software are primarily at risk.

Does EMET help mitigate attacks that could attempt to exploit this vulnerability? 
Yes. The Enhanced Mitigation Experience Toolkit (EMET) enables users to manage security mitigation technologies that help make it more difficult for attackers to exploit vulnerabilities in a given piece of software. EMET helps to mitigate this vulnerability in affected software on systems where EMET is installed and configured to work with the affected software.

For more information about EMET, see The Enhanced Mitigation Experience Toolkit.

What does the update do? 
The update addresses the vulnerability by correcting the way the affected software handles TIFF files.

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-2013-3906. This vulnerability was first described in Microsoft Security Advisory 2896666.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
Yes. Microsoft is aware of targeted attacks that attempt to exploit this vulnerability in Microsoft Office products.

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 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 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-KB2901674-x86.msu
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2901674-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 2901674
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-KB2901674-x86.msu
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2901674-x64.msu
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2901674-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 2901674
Registry key verificationNote A registry key does not exist to validate the presence of this update.

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-kb2850047-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 2850047
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-kb2817641-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 2817641
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-kb2817670-fullfile-x86-glb.exe
For all supported editions of Microsoft Office 2010 (64-bit editions):
ogl2010-kb2817670-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 2817670
Registry key verificationNot applicable

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) (2899397):
lync.msp
 For Microsoft Lync 2010 (64-bit) (2899397):
lync.msp
For Microsoft Lync 2010 Attendee (user level install) (2899393):
AttendeeUser.msp
For Microsoft Lync 2010 Attendee (admin level install) (2899395):
AttendeeAdmin.msp
For Microsoft Lync 2013 (32-bit) and Microsoft Lync Basic 2013 (32-bit):
lyncloc2013-kb2850057-fullfile-x86-glb.exe
For Microsoft Lync 2013 (64-bit) and Microsoft Lync Basic 2013 (64-bit):
lyncloc2013-kb2850057-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 2899397
For Microsoft Lync 2010 Attendee (user level install):
See Microsoft Knowledge Base Article 2899393
For Microsoft Lync 2010 Attendee (admin level install):
See Microsoft Knowledge Base Article 2899395
For all supported editions of Microsoft Lync 2013:
See Microsoft Knowledge Base Article 2850057
Registry Key VerificationFor Microsoft Lync 2010 (32-bit):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4415
For Microsoft Lync 2010 (64-bit):
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4415
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.4415
For Microsoft Lync 2010 Attendee (user level install):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22}
Version = 7577.4415
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:

  • Haifei Li of McAfee Labs IPS Team for reporting the Microsoft Graphics Component Memory Corruption Vulnerability (CVE-2013-3906)

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 (December 10, 2013): Bulletin published.
  • V1.1 (December 10, 2013): Clarified that users should undo the Disable the TIFF Codec workaround and the Disable data collaboration in Lync workaround after applying the update. See the Update FAQ for more information. Added undo steps to the Disable data collaboration in Lync workaround. These are informational changes only.
  • V1.2 (December 20, 2013): Revised the Based on the configuration of my system, how do I know if my system is affected? Update FAQ to include the updates that are applicable for each configuration. This is an informational change only.

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.