Microsoft Security Bulletin MS14-058 - Critical
Vulnerabilities in Kernel-Mode Driver Could Allow Remote Code Execution (3000061)
Published: October 14, 2014
Version: 1.0
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in Microsoft Windows. The more severe of the vulnerabilities could allow remote code execution if an attacker convinces a user to open a specially crafted document or to visit an untrusted website that contains embedded TrueType fonts. In all cases, however, an attacker would have no way to force users to perform these actions. Instead, an attacker would have to persuade users to do so, typically by getting them to click a link in an email message or Instant Messenger message.
This security update is rated Critical for all supported releases of Microsoft Windows. For more information, see the Affected Software section.
The security update addresses the vulnerabilities by correcting how the Windows kernel-mode driver handles objects in memory and the way it handles TrueType fonts. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability later in this bulletin.
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. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871. For customers who do not have automatic updating enabled, the steps in Turn automatic updating on or off can be used to enable automatic updating.
For administrators and enterprise installations, or end users who want to install this security update manually (including customers who have not enabled automatic updating), Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service. The updates are also available via the download links in the Affected Software table later in this bulletin.
For additional guidance, see the Detection and Deployment Tools and Guidance section in this bulletin.
Knowledge Base Article
- Knowledge Base Article: 3000061
- File Information: Yes
- SHA1/SHA2 hashes: Yes
- Known issues: None
Affected Software
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.
Affected Software
| Operating System | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|
| Windows Server 2003 | |||
| Windows Server 2003 Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2003 x64 Edition Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2003 with SP2 for Itanium-based Systems (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Vista | |||
| Windows Vista Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Vista x64 Edition Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 | |||
| Windows Server 2008 for 32-bit Systems Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 for x64-based Systems Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 7 | |||
| Windows 7 for 32-bit Systems Service Pack 1 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 7 for x64-based Systems Service Pack 1 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 R2 | |||
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 8 and Windows 8.1 | |||
| Windows 8 for 32-bit Systems (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 8 for x64-based Systems (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 8.1 for 32-bit Systems (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows 8.1 for x64-based Systems (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2012 and Windows Server 2012 R2 | |||
| Windows Server 2012 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2012 R2 (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows RT and Windows RT 8.1 | |||
| Windows RT[1](3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows RT 8.1[1](3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Server Core installation option | |||
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2012 (Server Core installation) (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
| Windows Server 2012 R2 (Server Core installation) (3000061) | Remote Code Execution | Critical | 2930275 in MS14-015 |
[1]This update is available via Windows Update.
Update FAQ
Are Windows Technical Preview and Windows Server Technical Preview affected by any of the vulnerabilities addressed in this bulletin?
Yes. Windows Technical Preview and Windows Server Technical Preview are affected by critical vulnerabilities addressed in this bulletin. Customers running these operating systems are encouraged to apply the update to their systems. The updates are available on Windows Update.
.gif) Note: |
|---|
| Note In some cases, not every update listed for a vulnerability will apply to the affected software installed on your system. |
I am running Windows 8.1, Windows Server 2012 R2, or Windows RT 8.1. Why am I not being offered the 3000061 update?
To be offered any security updates on Windows 8.1, Windows Server 2012 R2, or Windows RT 8.1, the 2919355 update must be installed on the system. For more information, see Microsoft Knowledge Base Article 2919355.
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, then select the country 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.
Severity Ratings and Vulnerability Identifiers
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 October bulletin summary. For more information, see Microsoft Exploitability Index.
| Vulnerability Severity Rating and Maximum Security Impact by Affected Software | |||
|---|---|---|---|
| Affected Software | Win32k.sys Elevation of Privilege Vulnerability - CVE-2014-4113 | TrueType Font Parsing Remote Code Execution Vulnerability - CVE-2014-4148 | Aggregate Severity Rating |
| Windows Server 2003 | |||
| Windows Server 2003 Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2003 x64 Edition Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2003 with SP2 for Itanium-based Systems (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Vista | |||
| Windows Vista Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Vista x64 Edition Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 | |||
| Windows Server 2008 for 32-bit Systems Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 for x64-based Systems Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 7 | |||
| Windows 7 for 32-bit Systems Service Pack 1 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 7 for x64-based Systems Service Pack 1 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 R2 | |||
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 8 and Windows 8.1 | |||
| Windows 8 for 32-bit Systems (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 8 for x64-based Systems (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 8.1 for 32-bit Systems (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows 8.1 for x64-based Systems (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2012 and Windows Server 2012 R2 | |||
| Windows Server 2012 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2012 R2 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows RT and Windows RT 8.1 | |||
| Windows RT (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows RT 8.1 (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Server Core installation option | |||
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2012 (Server Core installation) (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
| Windows Server 2012 R2 (Server Core installation) (3000061) | Important Elevation of Privilege | Critical Remote Code Execution | Critical |
Win32k.sys Elevation of Privilege Vulnerability - CVE-2014-4113
An elevation of privilege vulnerability exists when the Windows kernel-mode driver improperly handles objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-2014-4113.
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 must have valid logon credentials and be able to log on locally to exploit this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
FAQ
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Windows kernel-mode driver (win32k.sys) improperly handles objects in memory.
What is the Windows kernel-mode driver (win32k.sys)?
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the Graphics Device Interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).
What is NULL page mapping?
The “NULL page” is the area of system memory that starts with address 0x00000000. The NULL page is not typically allocated or mapped, so if the kernel dereferences a NULL pointer the usual result is a blue-screen condition. However, a blue-screen condition can be avoided if the NULL page is mapped, and because the NULL page resides in the user-mode memory address space, the attacker can allocate memory to take control of execution flow on behalf of the current user. This attack vector is not viable when NULL page mapping is disabled, which is the default state in Windows 8 and newer operating systems.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability 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.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by running a specially crafted application on an affected system. This could be achieved through obtaining valid logon credentials and logging on to the system or convincing a logged on, authenticated, user to execute an application on the attacker’s behalf.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this. Although all supported releases of Microsoft Windows are affected by this vulnerability, 32-bit and 64-bit editions of Windows 8 and Windows 8.1 are less exposed to currently known exploits due to mitigations built into these operating systems.
What does the update do?
The update addresses the vulnerability by correcting how the Windows kernel-mode driver handles objects in memory.
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?
Yes. Microsoft is aware of limited attacks that attempt to exploit this vulnerability.
TrueType Font Parsing Remote Code Execution Vulnerability - CVE-2014-4148
A remote code execution vulnerability exists when the Windows kernel-mode driver improperly handles TrueType fonts. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-2014-4148.
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:
- For an attack to be successful, a user must visit an untrusted website containing a specially crafted TrueType font file, or open the file as an email attachment. In all cases, however, an attacker would have no way to force users to perform these actions. Instead, an attacker would have to persuade users to do so, typically by getting them to click a link in an email message or Instant Messenger message.
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:
Deny access to T2EMBED.DLL
On Windows Server 2003:For 32-bit systems, enter the following command at an administrative command prompt:
Echo y| cacls "%windir%\system32\t2embed.dll" /E /P everyone:NFor 64-bit systems, enter the following command at an administrative command prompt:
Echo y| cacls "%windir%\system32\t2embed.dll" /E /P everyone:N Echo y| cacls "%windir%\syswow64\t2embed.dll" /E /P everyone:N
On Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2:
For 32-bit systems, enter the following command at an administrative command prompt:
Takeown.exe /f "%windir%\system32\t2embed.dll" Icacls.exe "%windir%\system32\t2embed.dll" /deny everyone:(F)For 64-bit systems, enter the following command at an administrative command prompt:
Takeown.exe /f "%windir%\system32\t2embed.dll" Icacls.exe "%windir%\system32\t2embed.dll" /deny everyone:(F) Takeown.exe /f "%windir%\syswow64\t2embed.dll" Icacls.exe "%windir%\syswow64\t2embed.dll" /deny everyone:(F)
Impact of Workaround. Applications that rely on embedded font technology will fail to display properly.
How to undo the workaround.
On Windows Server 2003:
For 32-bit systems, enter the following command at an administrative command prompt:
cacls "%windir%\system32\t2embed.dll" /E /R everyoneFor 64-bit systems, enter the following command at an administrative command prompt:
cacls "%windir%\system32\t2embed.dll" /E /R everyone cacls "%windir%\syswow64\t2embed.dll" /E /R everyone
On Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2:
For 32-bit systems, enter the following command at an administrative command prompt:
Icacls.exe %WINDIR%\system32\t2embed.DLL /remove:d everyoneFor 64-bit systems, enter the following command at an administrative command prompt:
Icacls.exe %WINDIR%\system32\t2embed.DLL /remove:d everyone Icacls.exe %WINDIR%\syswow64\t2embed.DLL /remove:d everyone
FAQ
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when a Windows kernel-mode driver fails to properly handles TrueType fonts.
What is the Windows kernel-mode driver (win32k.sys)?
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the Graphics Device Interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability 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.
How could an attacker exploit the vulnerability?
There are multiple means by which an attacker could exploit this vulnerability, including convincing a user to open a specially crafted document or to visit an untrusted webpage that contains embedded TrueType fonts. The specially crafted TrueType font could then exploit the vulnerability.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update addresses the vulnerability by correcting how the Windows kernel-mode driver handles TrueType fonts.
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?
Yes. Microsoft is aware of limited attacks that attempt to exploit this vulnerability.
Detection and Deployment Tools and Guidance
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.
Security Update Deployment
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software.
| Security update file names | For all supported 32-bit editions of Windows Server 2003:\ WindowsServer2003-KB3000061-86-ENU.exe |
|---|---|
| \ | For all supported x64-based editions of Windows Server 2003:\ WindowsServer2003-KB3000061-x64-ENU.exe |
| \ | For all supported Itanium-based editions of Windows Server 2003:\ WindowsServer2003-KB3000061-ia64-ENU.exe |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Update Log File | KB3000061.log |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB3000061$\Spuninst folder |
| File information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB3000061\Filelist |
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software.
| Security update file names | For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB3000061-x86.msu |
|---|---|
| \ | For all supported x64-based editions of Windows Vista:\ Windows6.0-KB3000061-x64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | WUSA.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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note 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 names | For all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB3000061-x86.msu |
|---|---|
| \ | For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB3000061-x64.msu |
| \ | For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB3000061-ia64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | WUSA.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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note 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 name | For all supported 32-bit editions of Windows 7:\ Windows6.1-KB3000061-x86.msu |
|---|---|
| \ | For all supported x64-based editions of Windows 7:\ Windows6.1-KB3000061-x64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | To 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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note 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 name | For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB3000061-x64.msu |
|---|---|
| \ | For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB3000061-ia64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | To 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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note A registry key does not exist to validate the presence of this update. |
Windows 8 and Windows 8.1 (all editions)
Reference Table
The following table contains the security update information for this software.
| Security update file name | For all supported 32-bit editions of Windows 8:\ Windows8-RT-KB3000061-x86.msu |
|---|---|
| \ | For all supported x64-based editions of Windows 8:\ Windows8-RT-KB3000061-x64.msu |
| \ | For all supported 32-bit editions of Windows 8.1:\ Windows8.1-KB3000061-x86.msu |
| \ | For all supported x64-based editions of Windows 8.1:\ Windows8.1-KB3000061-x64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | To 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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note A registry key does not exist to validate the presence of this update. |
Windows Server 2012 and Windows Server 2012 R2 (all editions)
Reference Table
The following table contains the security update information for this software.
| Security update file name | For all supported editions of Windows Server 2012:\ Windows8-RT-KB3000061-x64.msu |
|---|---|
| \ | For all supported editions of Windows Server 2012 R2:\ Windows8.1-KB3000061-x64.msu |
| Installation switches | See Microsoft Knowledge Base Article 934307 |
| Restart requirement | Yes, you must restart your system after you apply this security update. |
| Removal information | To 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 information | See Microsoft Knowledge Base Article 3000061 |
| Registry key verification | Note A registry key does not exist to validate the presence of this update. |
Windows RT and Windows RT 8.1 (all editions)
Reference Table
The following table contains the security update information for this software.
| Deployment | These updates are available via Windows Update only. |
|---|---|
| Restart Requirement | Yes, you must restart your system after you apply this security update. |
| Removal Information | 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 Information | See Microsoft Knowledge Base Article 3000061 |
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- CrowdStrike Intelligence Team for working with us on the Win32k.sys Elevation of Privilege Vulnerability (CVE-2014-4113)
- FireEye, Inc. for working with us on the Win32k.sys Elevation of Privilege Vulnerability (CVE-2014-4113)
- FireEye, Inc. for working with us on the TrueType Font Parsing Remote Code Execution Vulnerability (CVE-2014-4148)
Other Information
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
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
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 (October 14, 2014): Bulletin published.
Page generated 2014-10-16 9:19Z-07:00.