Microsoft Security Bulletin MS16-132 - Critical

Security Update for Microsoft Graphics Component (3199120)

Published: November 8, 2016 | Updated: December 13, 2016

Version: 2.0

This security update resolves vulnerabilities in Microsoft Windows. The most severe of the vulnerabilities could allow a remote code execution. The vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. 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.

This security update is rated Critical for all supported releases of Microsoft Windows. For more information, see the Affected Software and Vulnerability Severity Ratings section.

The security update addresses the vulnerabilities by correcting how the ATMFD component, the Windows Animation Manager, and the Windows Media Foundation handle objects in memory.
For more information about this update, see Microsoft Knowledge Base Article 3199120.

The following software versions or editions are affected. Versions or editions that are not listed 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.

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 November bulletin summary.

Operating System

Open Type Font Information Disclosure Vulnerability
CVE-2016-7210

Windows Animation Manager Memory Corruption Vulnerability
CVE-2016-7205

Media Foundation Memory Corruption Vulnerability
CVE-2016-7217

Open Type Font Remote Code Execution Vulnerability
CVE-2016-7256

Updates Replaced*             

Windows Vista

Windows Vista Service Pack 2
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Vista x64 Edition Service Pack 2
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008 for x64-based Systems Service Pack 2
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008 for Itanium-based Systems Service Pack 2
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows 7

Windows 7 for 32-bit Systems Service Pack 1
(3197867)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

None

Windows 7 for 32-bit Systems Service Pack 1
(3197868)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3185330

Windows 7 for x64-based Systems Service Pack 1
(3197867)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

None

Windows 7 for x64-based Systems Service Pack 1
(3197868)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3185330

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1
(3197867)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

None

Windows Server 2008 R2 for x64-based Systems Service Pack 1
(3197868)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3185330

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(3197867)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

None

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(3197868)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3185330

Windows 8.1

Windows 8.1 for 32-bit Systems
(3197873)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows 8.1 for 32-bit Systems
(3197874)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185331

Windows 8.1 for x64-based Systems
(3197873)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows 8.1 for x64-based Systems
(3197874)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185331

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012
(3197876)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows Server 2012
(3197877)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185332

Windows Server 2012 R2
(3197873)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows Server 2012 R2
(3197874)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185331

Windows RT 8.1

Windows RT 8.1[1]
(3197874)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185331

Windows 10

Windows 10 for 32-bit Systems [2]
(3198585)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3192440

Windows 10 for x64-based Systems [2]
(3198585)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3192440

Windows 10 Version 1511 for 32-bit Systems [2]
(3198586)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3192441

Windows 10 Version 1511 for x64-based Systems [2]
(3198586)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3192441

Windows 10 Version 1607 for 32-bit Systems [2]
(3200970)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3194798

Windows 10 Version 1607 for x64-based Systems [2]
(3200970)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3194798

Windows Server 2016

Windows Server 2016 for x64-based Systems [2]
(3200970)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3194798

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(3203859)

Important 
Information Disclosure

Not applicable

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(3197867)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3164033 in MS16-074

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(3197868)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Not applicable

Critical 
Remote Code Execution

3185330

Windows Server 2012 (Server Core installation)
(3197876)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows Server 2012 (Server Core installation)
(3197877)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185332

Windows Server 2012 R2 (Server Core installation)
(3197873)
Security Only[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

None

Windows Server 2012 R2 (Server Core installation)
(3197874)
Monthly Rollup[3]

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3185331

Windows Server 2016 for x64-based Systems (Server Core installation) [2]
(3200970)

Important 
Information Disclosure

Critical 
Remote Code Execution

Important
Remote Code Execution

Critical 
Remote Code Execution

3194798

[1]This update is available via Windows Update only.

[2]Windows 10 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The update is available via the Windows Update Catalog.

[3]Beginning with the October 2016 release, Microsoft is changing the update servicing model for Windows 7, Windows Server 2008 R2, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. For more information, please see this Microsoft TechNet article.

Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5. To be protected from the vulnerability, Microsoft recommends that customers running this operating system apply the current update, which is available from Windows Update

*The Updates Replaced column shows only the latest update in any chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update KB number, and then view update details (updates replaced information is provided on the Package Details tab).

Open Type Font Information Disclosure Vulnerability – CVE-2016-7210

An information disclosure vulnerability exists when the ATMFD component improperly discloses the contents of its memory. An attacker who successfully exploited the vulnerability could obtain information to further compromise the user’s system.

There are multiple ways an attacker could exploit the vulnerability, such as by convincing a user to open a specially crafted document, or by convincing a user to visit an untrusted webpage. The update addresses the vulnerability by correcting how the ATMFD component handle objects in memory.

The following table contains a link to the standard entry for the vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly disclosed

Exploited

Open Type Font Information Disclosure Vulnerability

CVE-2016-7210

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

The following workarounds may be helpful in your situation:

  • Rename ATMFD.DLL
    For 32-bit systems:
    1. Enter the following commands at an administrative command prompt:
      cd "%windir%\system32"
      takeown.exe /f atmfd.dll
      icacls.exe atmfd.dll /save atmfd.dll.acl
      icacls.exe atmfd.dll /grant Administrators:(F) 
      rename atmfd.dll x-atmfd.dll
      
    2. Restart the system.

       

    For 64-bit systems:

    1. Enter the following commands at an administrative command prompt:
      cd "%windir%\system32"
      takeown.exe /f atmfd.dll
      icacls.exe atmfd.dll /save atmfd.dll.acl
      icacls.exe atmfd.dll /grant Administrators:(F) 
      rename atmfd.dll x-atmfd.dll
      cd "%windir%\syswow64"
      takeown.exe /f atmfd.dll
      icacls.exe atmfd.dll /save atmfd.dll.acl
      icacls.exe atmfd.dll /grant Administrators:(F) 
      rename atmfd.dll x-atmfd.dll
      
    2. Restart the system.

     

    Optional procedure for Windows 8 and later operating systems (disable ATMFD):

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Method 1 (manually edit the system registry):

  • Run regedit.exe as Administrator.
  • In Registry Editor, navigate to the following sub key (or create it) and set its DWORD value to 1:

    HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\DisableATMFD, DWORD = 1

  • Close Registry Editor and restart the system.

     

    Method 2 (use a managed deployment script):

  • Create a text file named ATMFD-disable.reg that contains the following text:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
    "DisableATMFD"=dword:00000001
    
  • Run regedit.exe.
  • In Registry Editor, click the File menu and then click Import.
  • Navigate to and select the ATMFD-disable.reg file that you created in the first step.
    (Note If your file is not listed where you expect it to be, ensure that it has not been automatically given a .txt file extension, or change the dialog’s file extension parameters to All Files).
  • Click Open and then click OK to close Registry Editor.

     

    Impact of workaround. Applications that rely on embedded font technology will not display properly. Disabling ATMFD.DLL could cause certain applications to stop working properly if they use OpenType fonts. Microsoft Windows does not release any OpenType fonts natively. However, third-party applications could install them and they could be affected by this change.

    How to undo the workaround. 

    For 32-bit systems:

    1. Enter the following commands at an administrative command prompt:
      cd "%windir%\system32"
      rename x-atmfd.dll atmfd.dll
      icacls.exe atmfd.dll /setowner "NT SERVICE\TrustedInstaller"
      icacls.exe . /restore atmfd.dll.acl
      
    2. Restart the system.

     

    For 64-bit systems:

    1. Enter the following commands at an administrative command prompt:
      cd "%windir%\system32"
      rename x-atmfd.dll atmfd.dll
      icacls.exe atmfd.dll /setowner "NT SERVICE\TrustedInstaller"
      icacls.exe . /restore atmfd.dll.acl
      cd "%windir%\syswow64"
      rename x-atmfd.dll atmfd.dll
      icacls.exe atmfd.dll /setowner "NT SERVICE\TrustedInstaller"
      icacls.exe . /restore atmfd.dll.acl
      
    2. Restart the system.

       

    Optional procedure for Windows 8 and later operating systems (enable ATMFD):

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Method 1 (manually edit the system registry):

  • Run regedit.exe as Administrator.
  • In Registry Editor, navigate to the following sub key and set its DWORD value to 0:

    HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\DisableATMFD, DWORD = 0

  • Close Registry Editor and restart the system.

     

    Method 2 (use a managed deployment script):

  • Create a text file named ATMFD-enable.reg that contains the following text:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
    "DisableATMFD"=dword:00000000
    
    1. Run regedit.exe.
  • In Registry Editor, click the File menu and then click Import.
  • Navigate to and select the ATMFD-enable.reg file that you created in the first step.
    (Note If your file is not listed where you expect it to be, ensure that it has not been automatically given a .txt file extension, or change the dialog’s file extension parameters to All Files).
  • Click Open and then click OK to close Registry Editor.

Windows Animation Manager Memory Corruption Vulnerability – CVE-2016-7205

A remote code execution vulnerability exists when the Windows Animation Manager improperly handles objects in memory. An attacker who successfully exploited the vulnerability could install programs; view, change, or delete data; or create new accounts with full user rights.

An attacker could exploit the vulnerability by convincing a user to visit a malicious webpage. The security update addresses the vulnerability by correcting how the Windows Animation Manager handles objects in memory.

The following table contains a link to the standard entry for the vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly disclosed

Exploited

Windows Animation Manager Memory Corruption Vulnerability

CVE-2016-7205

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

The Microsoft has not identified any workarounds for this vulnerability.



Media Foundation Memory Corruption Vulnerability

A memory corruption vulnerability exists when the Windows Media Foundation improperly handles objects in memory. An attacker who successfully exploited the vulnerability could install programs; view, change, or delete data; or create new accounts with full user rights.

There are multiple ways an attacker could exploit the vulnerability, such as by convincing a user to open a specially crafted document, or by convincing a user to visit a malicious webpage. The security update addresses the vulnerability by correcting how Windows Media Foundation handles objects in memory. The following table contains a link to the standard entry for the vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly disclosed

Exploited

Media Foundation Memory Corruption Vulnerability

CVE-2016-7217

No

No

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

The Microsoft has not identified any workarounds for this vulnerability.

Open Type Font Remote Code Execution Vulnerability – CVE-2016-7256

A remote code execution vulnerability exists when the Windows font library improperly handles specially crafted embedded fonts. An attacker who successfully exploits this vulnerability could take 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.

There are multiple ways an attacker could exploit the vulnerability:

•In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability and then convince users 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 or 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 the vulnerability, and then convince users to open the document file. The security update addresses the vulnerability by correcting how the Windows font library handles embedded fonts.

The following table contains a link to the standard entry for the vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability title

CVE number

Publicly disclosed

Exploited

Open Type Font Remote Code Execution Vulnerability

CVE-2016-7256

No

Yes

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

The following workarounds may be helpful in your situation:

Please see the workaround described in the vulnerability information for CVE-2016-7210.

For Security Update Deployment information see the Microsoft Knowledge Base article referenced here in the Executive Summary.

Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgments for more information.

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.

  • V1.0 (November 8, 2016): Bulletin published.
  • V2.0 (December 13, 2016): Revised bulletin to announce the following updates have been rereleased with a detection change that addresses a supersedence issue that certain customers experienced when attempting to install the November Security Only updates.
  • These are detection changes only. There were no changes to the update files. Customers who have already successfully installed any of these updates do not need to take any action. For more information, see the Microsoft Knowledge Base article for the respective update.
Page generated 2016-12-12 11:16-08:00.
Show: