Vulnerability in Windows NAT Driver Could Allow Denial of Service (2849568)
Published: August 13, 2013
This security update resolves a privately reported vulnerability in the Windows NAT Driver in Microsoft Windows. The vulnerability could allow denial of service if an attacker sends a specially crafted ICMP packet to a target server that is running the Windows NAT Driver service.
This security update is rated Important for all supported editions of Windows Server 2012. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting the way that Windows NAT Driver service validates memory addresses when handling specially crafted ICMP packets. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Most customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update 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.
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.
| Operating System |
| Windows XP Service Pack 3 |
| Windows XP Professional x64 Edition Service Pack 2 |
| Windows Server 2003 Service Pack 2 |
| Windows Server 2003 x64 Edition Service Pack 2 |
| Windows Server 2003 with SP2 for Itanium-based Systems |
| 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 64-bit Systems |
| Windows RT |
| 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 (Server Core installation) |
**How are Server Core installations** **affected by the vulnerability** **addressed in this bulletin?**
The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as indicated in the Non-Applicable Software table, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation: Overview](http://technet.microsoft.com/library/ee441255), [Servicing a Server Core Installation](http://technet.microsoft.com/library/ff698994), and [Server Core and Full Server Integration Overview](http://technet.microsoft.com/library/hh831758).
**MS13-064** **and** **MS13-065** **both address vulnerabilities leveraging ICMP. Are these** **security updates** **related?**
No. The security updates are not related. Customers should apply the updates for the software installed on their systems.
**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](http://go.microsoft.com/fwlink/?linkid=21742) 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](http://go.microsoft.com/fwlink/?linkid=169555). For more information about service packs for these software releases, see [Service Pack Lifecycle Support Policy](http://go.microsoft.com/fwlink/?linkid=89213).
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](http://go.microsoft.com/fwlink/?linkid=33329) 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](http://go.microsoft.com/fwlink/?linkid=169557).
### **Vulnerability Information**
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 [August bulletin summary](http://technet.microsoft.com/security/bulletin/ms13-aug). For more information, see [Microsoft Exploitability Index](http://technet.microsoft.com/security/cc998259).
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Windows NAT Denial of Service Vulnerability - CVE-2013-3182
Aggregate Severity Rating
Windows Server 2012
Denial of Service
Windows NAT Denial of Service Vulnerability - CVE-2013-3182
A denial of service vulnerability exists in the Windows NAT Driver that could cause the target system to stop responding until restarted.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2013-3182](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2013-3182).
#### Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Microsoft has not identified any workarounds for this vulnerability.
**What is the scope of the vulnerability?**
This is a denial of service vulnerability.
**What causes the vulnerability?**
The vulnerability is caused when the Windows NAT Driver service in Windows Server 2012 does not properly handle specially crafted ICMP packets leading to memory corruption.
**What** **is Windows NAT Driver service?**
The Windows NAT Driver (winnat) service provides network address translation (NAT) in Windows. The service is used by remote access features such as DirectAccess running on Windows Server 2012.
**What is** **Internet Control Message Protocol (ICMP)?**
Internet Control Message Protocol (ICMP) is an error reporting and diagnostic utility and is considered a required part of any IP implementation. For more information, see [Microsoft Knowledge Base Article 170292](http://support.microsoft.com/kb/170292).
**What might an attacker use the vulnerability to do?**
An unauthenticated attacker who successfully exploited this vulnerability could cause the target system to stop responding until restarted.
**How could an attacker exploit the** **vulnerability?**
An unauthenticated attacker could send specially crafted ICMP packets to the target server.
**What systems are primarily at risk from the vulnerability?**
Windows Server 2012 servers are affected by this vulnerability.
**What does the update do?**
The update addresses the vulnerability by correcting the way that the Windows NAT Driver service validates memory addresses when handling specially crafted ICMP packets.
**When this security bulletin was issued, had this vulnerability been publicly disclosed?**
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
**When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?**
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
### Update Information
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](http://technet.microsoft.com/security/cc297183).
Security Update Deployment
For information about the specific security update for your affected software, click the appropriate link:
#### Windows Server 2012 (all editions)
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-KB2849568-x64.msu
Yes, you must restart your system after you apply this security update.
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.
Note A registry key does not exist to validate the presence of this update.
### 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](http://go.microsoft.com/fwlink/?linkid=215201).
**How to obtain help and support for this security update**
- Help installing updates: [Support for Microsoft Update](http://support.microsoft.com/ph/6527)
- Security solutions for IT professionals: [TechNet Security Troubleshooting and Support](http://technet.microsoft.com/security/bb980617.aspx)
- Help protect your computer that is running Windows from viruses and malware: [Virus Solution and Security Center](http://support.microsoft.com/contactus/cu_sc_virsec_master)
- Local support according to your country: [International Support](http://support.microsoft.com/common/international.aspx)
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 (August 13, 2013): Bulletin published.
*Built at 2014-04-18T13:49:36Z-07:00*