Export (0) Print
Expand All

Microsoft Security Bulletin MS14-002 - Important

Vulnerability in Windows Kernel Could Allow Elevation of Privilege (2914368)

Published: January 14, 2014

Version: 1.0

General Information

Executive Summary

This security update resolves a publicly reported vulnerability in Microsoft Windows. The vulnerability could allow elevation of privilege if an attacker logs on to a system and runs a specially crafted application. An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.

This security update is rated Important for all supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correctly validating input passed to the Windows Kernel component. 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 also addresses the vulnerability first described in Microsoft Security Advisory 2814486.

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 at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Knowledge Base Article

  • Knowledge Base Article: 2914368
  • File Information: Yes
  • SHA1/SHA2 hashes: Yes
  • Known issues: None

 

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 System

Maximum Security Impact

Aggregate Severity Rating

Updates Replaced

Windows XP

Windows XP Service Pack 3
(2914368)

Elevation of Privilege

Important

2440591 in MS10-099

Windows XP Professional x64 Edition Service Pack 2
(2914368)

Elevation of Privilege

Important

2440591 in MS10-099

Windows Server 2003

Windows Server 2003 Service Pack 2
(2914368)

Elevation of Privilege

Important

2440591 in MS10-099

Windows Server 2003 x64 Edition Service Pack 2
(2914368)

Elevation of Privilege

Important

2440591 in MS10-099

Windows Server 2003 with SP2 for Itanium-based Systems
(2914368)

Elevation of Privilege

Important

2440591 in MS10-099

 

Non-Affected Software

Operating System

Windows Vista Service Pack 2

Windows Vista x64 Edition Service Pack 2

Windows Server 2008 for 32-bit Systems Service Pack 2

Windows Server 2008 for x64-based Systems Service Pack 2

Windows Server 2008 for Itanium-based Systems Service Pack 2

Windows 7 for 32-bit Systems Service Pack 1

Windows 7 for x64-based Systems Service Pack 1

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1

Windows 8 for 32-bit Systems

Windows 8 for x64-based Systems

Windows 8.1 for 32-bit Systems

Windows 8.1 for x64-based Systems

Windows Server 2012

Windows Server 2012 R2

Windows RT

Windows RT 8.1

Server Core installation option

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

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

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)

Windows Server 2012 R2 (Server Core installation)

Windows Server 2012 (Server Core installation)

 

If I applied the workaround previously described in Microsoft Security Advisory 2914486, should I undo the workaround before or after applying this update? 
Yes, customers should undo the workaround before applying this update. If you do not undo the workaround at some point, services that rely on Telephony Application Programming Interfaces (TAPI) will not function. These services include Remote Access Service (RAS), dial-up networking, and virtual private networking (VPN).

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.

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software

Affected Software

Kernel NDProxy Vulnerability - CVE-2013-5065

Aggregate Severity Rating

Windows XP

Windows XP Service Pack 3

Important 
Elevation of Privilege

Important

Windows XP Professional x64 Edition Service Pack 2

Important 
Elevation of Privilege

Important

Windows Server 2003

Windows Server 2003 Service Pack 2

Important 
Elevation of Privilege

Important

Windows Server 2003 x64 Edition Service Pack 2

Important 
Elevation of Privilege

Important

Windows Server 2003 with SP2 for Itanium-based Systems

Important 
Elevation of Privilege

Important

An elevation of privilege vulnerability exists in the NDProxy component of the Windows kernel due to improper validation of input passed from user mode to the kernel. The vulnerability could allow an attacker to run code in kernel mode. An attacker who successfully exploited this vulnerability could run a specially crafted application and take complete control of an affected system. The attacker could then install programs; view, change, or delete data; or create new accounts with full administrator rights.

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

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. The vulnerability could not be exploited remotely or by anonymous users.

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:

  • Reroute the NDProxy service to Null.sys

    For environments with non-default, limited user privileges, Microsoft has verified that the following workaround effectively blocks the attacks that have been observed in the wild.

    To implement this workaround, follow these steps:

    1. From an elevated command prompt, execute the following commands:
      sc stop ndproxy
      reg add HKLM\System\CurrentControlSet\Services\ndproxy /v ImagePath /t REG_EXPAND_SZ /d system32\drivers\null.sys /f
      
    2. Restart the system.

     

    Impact of workaround. Disabling NDProxy.sys will cause certain services that rely on Windows Telephony Application Programming Interfaces (TAPI) to not function. Services that will no longer work include Remote Access Service (RAS), dial-up networking, and virtual private networking (VPN).

    How to undo the workaround. 

    To undo this workaround, follow these steps:

    1. From an elevated command prompt, execute the following commands:
      sc stop ndproxy
      reg add HKLM\System\CurrentControlSet\Services\ndproxy /v ImagePath /t REG_EXPAND_SZ /d system32\drivers\ndproxy.sys /f
      
    2. Restart the system.

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 NDProxy.sys kernel component fails to properly validate input.

What is NDPROXY? 
NDPROXY is a system-provided driver that interfaces WAN miniport drivers, call managers, and miniport call managers to the Telephony Application Programming Interfaces (TAPI) services. For additional information, see MSDN article, NDPROXY Overview.

What might an attacker use the vulnerability to do? 
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.

How could an attacker exploit the vulnerability? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over the affected system.

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 correctly validating input passed to the Windows Kernel component.

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-5065. This vulnerability was first described in Microsoft Security Advisory 2914486.

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

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

Windows XP (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 XP:
WindowsXP-KB2914368-x86-ENU.exe


For all supported x64-based editions of Windows XP Professional:
WindowsServer2003.WindowsXP-KB2914368-x64-ENU.exe

Installation switches

See Microsoft Knowledge Base Article 262841

Update log file

KB2914368.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%\$NTUninstallKB2914368$\Spuninst folder

File information

See Microsoft Knowledge Base Article 2914368

Registry key verification

For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2914368\Filelist


For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2914368\Filelist

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

 

Windows Server 2003 (all editions)

Reference Table

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

Security update file names

For all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB2914368-x86-ENU.exe


For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2914368-x64-ENU.exe


For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2914368-ia64-ENU.exe

Installation switches

See Microsoft Knowledge Base Article 262841

Update log file

KB2914368.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%\$NTUninstallKB2914368$\Spuninst folder

File information

See Microsoft Knowledge Base Article 2914368

Registry key verification

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2914368\Filelist

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

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

  • FireEye, Inc. for helping us with the Kernel NDProxy Vulnerability (CVE-2013-5065)

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 (January 14, 2014): Bulletin published.
Page generated 2014-06-25 13:41Z-07:00.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft