MS12-017: Vulnerability in DNS Server could allow denial of service: March 13, 2012

• Home users:
  http://www.microsoft.com/security/pc-security/bulletins/201203.aspx

  (http://www.microsoft.com/security/pc-security/bulletins/201203.aspx)
  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update website now:
  http://update.microsoft.com/microsoftupdate/

  (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://technet.microsoft.com/security/bulletin/MS12-017

  (http://technet.microsoft.com/security/bulletin/MS12-017)

How to obtain help and support for this security update

Back to the top | Give Feedback

Known issues with this security update

• Symptoms
  After you install this security update, the DNS Server service may not start, or you may receive an access violation error message shortly after the service starts, or after the operating system starts.
  
  Cause
  This issue may occur if DNS is configured to have a CNAME and a SOA record that both exist for the "@" record. The "@" record identifies the root of a DNS zone. This can frequently be identified in the DNS Manager as a record with the "(same as parent folder)" name. The SOA and NS records are allowed in this folder. RFC 2181 describes name uniqueness checks for CNAME records. According to RFC 2181, the CNAME may not exist in the “same as parent folder" ("@") of a zone.
  
  Workaround
  To avoid this issue, identify and remove the "@" CNAME record that is causing the issue from the misconfigured zone before you install security update 2647170.
  
  To help identify problematic zones, run the following sample PowerShell script. PowerShell is installed by default in Windows Server 2008 R2. PowerShell must be installed as a feature in Windows Server 2008 and must be manually installed in Windows Server 2003.
  
  $count = 0
  $var = get-wmiobject -query "select * from win32_service where name = 'dns'"
  if ($var -ne $null)
  {
  if ($var.state.tolower() -eq "running")
  {
  [array] $global:badcnamedomains = $null
  $var = get-wmiobject -namespace "root\microsoftdns" -query "select * from microsoftdns_zone"
  if ($var -ne $null)
  {
  foreach ($var2 in $var)
  {
  $query = "select * from microsoftdns_cnametype where containername = '" + $var2.name + "'"
  $var3 = get-wmiobject -namespace "root\microsoftdns" -query $query | where {$_.ownername -eq $var2.name}
  if ($var3 -ne $null)
  {
  $count += 1
  $global:badcnamedomains += $var3.domainname
  }
  }
  }
  else
  {
  write-host "No zones returned"
  }
  }
  }
  if ($count -gt 0)
  {
  write-host "Total number of zones found: $count"
  write-host "The zones are:"
  write-host $global:badcnamedomains
  }
  elseif ($count -eq 0)
  {
  write-host "No zones found with the issue"
  }
  $count = $null
  $global:badcnamedomains = $null
  
  
  
  Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
  
  To run the sample PowerShell script, copy the text, and then paste it into a PowerShell Command Prompt window that is running with administrative permissions. The script will identify CNAME records that conflict with SOA records in locally held DNS zones. To delete the CNAME records that do not comply with RFC 2181, type the following command at command prompt, and then press Enter:
  DNSCMD /recorddelete DNS zone name @ cname
  
  To resolve the problem if the access violation error has already occurred
  If you already have installed security update 2647170 before removing the offending CNAME record, you may have to roll back to the previously installed version of DNS. Then, remove the conflicting @ CNAME record from the misconfigured zone, and then reinstall security update 2647170.

Back to the top | Give Feedback

Windows Server 2003 file information

• The files that apply to a specific milestone (SPn) and service branch (QFE, GDR) are noted in the "SP requirement" and "Service branch" columns.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
• In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2003

For all supported x86-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

Windows Server 2008 file information

• The files that apply to a specific product, milestone (SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6002.18xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	GDR
  6.0.6002.22xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	LDR

• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Windows Server 2008 R2 file information

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.1.7600.16xxx	Windows Server 2008 R2	RTM	GDR
  6.1.7600.20xxx	Windows Server 2008 R2	RTM	LDR
  6.1.7601.17xxx	Windows Server 2008 R2	SP1	GDR
  6.1.7601.21xxx	Windows Server 2008 R2	SP1	LDR

• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

Back to the top | Give Feedback