Security Bulletin

Microsoft Security Bulletin MS12-054 - Critical

Vulnerabilities in Windows Networking Components Could Allow Remote Code Execution (2733594)

Published: August 14, 2012 | Updated: July 09, 2013

Version: 2.2

General Information

Executive Summary

This security update resolves four privately reported vulnerabilities in Microsoft Windows. The most severe of these vulnerabilities could allow remote code execution if an attacker sends a specially crafted response to a Windows print spooler request. Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems connected directly to the Internet have a minimal number of ports exposed.

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

The security update addresses the vulnerabilities by correcting how the Windows Print Spooler handles specially crafted responses and how Windows networking components handle Remote Administration Protocol (RAP) responses. For more information about the vulnerabilities, 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 immediately 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.

Known Issues. None

Affected and Non-Affected Software

The following software have 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 (KB2705219) Remote Code Execution Critical KB958644 in MS08-067 replaced by KB2705219
Windows XP Service Pack 3 (KB2712808) Remote Code Execution Critical KB961501 in MS09-022 replaced by KB2712808
Windows XP Professional x64 Edition Service Pack 2 (KB2705219) Remote Code Execution Critical KB958644 in MS08-067 replaced by KB2705219
Windows XP Professional x64 Edition Service Pack 2 (KB2712808) Remote Code Execution Critical KB961501 in MS09-022 replaced by KB2712808
Windows Server 2003
Windows Server 2003 Service Pack 2 (KB2705219) Denial of Service Important KB958644 in MS08-067 replaced by KB2705219
Windows Server 2003 Service Pack 2 (KB2712808) Remote Code Execution Critical KB961501 in MS09-022 replaced by KB2712808
Windows Server 2003 x64 Edition Service Pack 2 (KB2705219) Denial of Service Important KB958644 in MS08-067 replaced by KB2705219
Windows Server 2003 x64 Edition Service Pack 2 (KB2712808) Remote Code Execution Critical KB961501 in MS09-022 replaced by KB2712808
Windows Server 2003 with SP2 for Itanium-based Systems (KB2705219) Denial of Service Important KB958644 in MS08-067 replaced by KB2705219
Windows Server 2003 with SP2 for Itanium-based Systems (KB2712808) Remote Code Execution Critical KB961501 in MS09-022 replaced by KB2712808
Windows Vista
Windows Vista Service Pack 2 (KB2705219) Denial of Service Moderate None
Windows Vista Service Pack 2 (KB2712808) Denial of Service Important KB961501 in MS09-022 replaced by KB2712808
Windows Vista x64 Edition Service Pack 2 (KB2705219) Denial of Service Moderate None
Windows Vista x64 Edition Service Pack 2 (KB2712808) Denial of Service Important KB961501 in MS09-022 replaced by KB2712808
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2705219) Denial of Service Moderate None
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2712808) Denial of Service Moderate KB961501 in MS09-022 replaced by KB2712808
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2705219) Denial of Service Moderate None
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2712808) Denial of Service Moderate KB961501 in MS09-022 replaced by KB2712808
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2705219) Denial of Service Moderate None
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2712808) Denial of Service Moderate KB961501 in MS09-022 replaced by KB2712808
Windows 7
Windows 7 for 32-bit Systems (KB2705219) Denial of Service Moderate None
Windows 7 for 32-bit Systems (KB2712808) Denial of Service Moderate None
Windows 7 for 32-bit Systems Service Pack 1 (KB2705219) Denial of Service Moderate None
Windows 7 for 32-bit Systems Service Pack 1 (KB2712808) Denial of Service Moderate None
Windows 7 for x64-based Systems (KB2705219) Denial of Service Moderate None
Windows 7 for x64-based Systems (KB2712808) Denial of Service Moderate None
Windows 7 for x64-based Systems Service Pack 1 (KB2705219) Denial of Service Moderate None
Windows 7 for x64-based Systems Service Pack 1 (KB2712808) Denial of Service Moderate None
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems (KB2712808) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2712808) Denial of Service Moderate None
Windows Server 2008 R2 for Itanium-based Systems (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for Itanium-based Systems (KB2712808) Denial of Service Moderate None
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2712808) Denial of Service Moderate None
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (KB2705219) Denial of Service Moderate None
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (KB2712808) Denial of Service Moderate KB961501 in MS09-022 replaced by KB2712808
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (KB2705219) Denial of Service Moderate None
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (KB2712808) Denial of Service Moderate KB961501 in MS09-022 replaced by KB2712808
Windows Server 2008 R2 for x64-based Systems (Server Core installation) (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems (Server Core installation) (KB2712808) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (KB2705219) Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (KB2712808) Denial of Service Moderate None

I have already successfully installed the original KB2705219 update. Do I need to apply the KB2705219 update packages rereleased on October 9, 2012?
For Windows XP and Windows Server 2003, the rereleased update only applies to systems on which the original update has not been installed. Windows XP and Windows Server 2003 customers who have already successfully installed the original KB2705219 update on their systems do not need to take any action. These customers will not be reoffered this update if it is already installed on their systems.

For Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, customers need to apply the rereleased KB2705219 update packages.

Note Only the KB2705219 update was rereleased on October 9, 2012. The KB2712808 update was not part of the rerelease.

Why was this bulletin revised on October 9, 2012?
Microsoft revised this bulletin to rerelease the KB2705219 update for Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 to address an issue involving specific digital certificates that were generated by Microsoft without proper timestamp attributes. For more information, see Microsoft Security Advisory 2749655.

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

Where are the hashes of the security updates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2733594.

Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files.

There are multiple update packages available for some affected software. Do I need to install all the updates listed in the Affected Software table for the software?
Yes. Customers should apply all updates offered for the software installed on their systems.

Do I need to install these security updates in a particular sequence?
No. Multiple updates for one version of Microsoft Windows can be applied in any sequence.

I am running Windows Server 2008 R2 (Server Core installation), which islisted in the Affected Software table. Why am I not being offered the KB2712808 update?
The KB2712808 update is only offered to systems running a Server Core installation option of Windows Server 2008 R2 when the Printing-ServerCore-Role setting is enabled.

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 have 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.

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

Affected Software Remote Administration Protocol Denial of Service Vulnerability - CVE-2012-1850 Print Spooler Service Format String Vulnerability - CVE-2012-1851 Remote Administration Protocol Heap Overflow Vulnerability - CVE-2012-1852 Remote Administration Protocol Stack Overflow Vulnerability - CVE-2012-1853 Aggregate Severity Rating
Windows XP
Windows XP Service Pack 3 (KB2705219) Important  Denial of Service Not applicable Critical  Remote Code Execution Critical  Remote Code Execution Critical
Windows XP Service Pack 3 (KB2712808) Not applicable Critical  Remote Code Execution Not applicable Not applicable Critical
Windows XP Professional x64 Edition Service Pack 2 (KB2705219) Important  Denial of Service Not applicable Critical  Remote Code Execution Not applicable Critical
Windows XP Professional x64 Edition Service Pack 2 (KB2712808) Not applicable Critical  Remote Code Execution Not applicable Not applicable Critical
Windows Server 2003
Windows Server 2003 Service Pack 2 (KB2705219) Important  Denial of Service Not applicable Not applicable Not applicable Important
Windows Server 2003 Service Pack 2 (KB2712808) Not applicable Critical  Remote Code Execution Not applicable Not applicable Critical
Windows Server 2003 x64 Edition Service Pack 2 (KB2705219) Important  Denial of Service Not applicable Not applicable Not applicable Important
Windows Server 2003 x64 Edition Service Pack 2 (KB2712808) Not applicable Critical  Remote Code Execution Not applicable Not applicable Critical
Windows Server 2003 with SP2 for Itanium-based Systems (KB2705219) Important  Denial of Service Not applicable Not applicable Not applicable Important
Windows Server 2003 with SP2 for Itanium-based Systems (KB2712808) Not applicable Critical  Remote Code Execution Not applicable Not applicable Critical
Windows Vista
Windows Vista Service Pack 2 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Vista Service Pack 2 (KB2712808) Not applicable Important  Denial of Service Not applicable Not applicable Important
Windows Vista x64 Edition Service Pack 2 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Vista x64 Edition Service Pack 2 (KB2712808) Not applicable Important  Denial of Service Not applicable Not applicable Important
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows 7
Windows 7 for 32-bit Systems (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows 7 for 32-bit Systems (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows 7 for 32-bit Systems Service Pack 1 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows 7 for 32-bit Systems Service Pack 1 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows 7 for x64-based Systems (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows 7 for x64-based Systems (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows 7 for x64-based Systems Service Pack 1 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows 7 for x64-based Systems Service Pack 1 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2 for Itanium-based Systems (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for Itanium-based Systems (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems (Server Core installation) (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems (Server Core installation) (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (KB2705219) Moderate  Denial of Service Not applicable Not applicable Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) (KB2712808) Not applicable Moderate  Denial of Service Not applicable Not applicable Moderate

Remote Administration Protocol Denial of Service Vulnerability - CVE-2012-1850

A denial of service vulnerability exists in Windows networking components. The vulnerability is due to the service not properly handling specially crafted RAP requests. An attacker who successfully exploited this vulnerability could cause some of the Windows networking component to stop responding.

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

Mitigating Factors for Remote Administration Protocol Denial of Service Vulnerability - CVE-2012-1850

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:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems connected directly to the Internet have a minimal number of ports exposed.

Workarounds for Remote Administration Protocol Denial of Service Vulnerability - CVE-2012-1850

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:

  • Disable the LanmanWorkstation service

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    We recommend that you back up the registry before you edit it.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.

    2. In Registry Editor, expand the following registry location:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    3. Select LanmanWorkstation, and then click the File menu and select Export.

    4. In the Export Registry File dialog, type lanmanworkstation_configuration_backup.reg, and then click Save.

    5. Double-click the Start registry entry, change the Valuedata field to 4, and then click OK.

    6. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    Using a managed deployment script:

    1. Make a backup copy of the registry keys using a managed deployment script with the following command:

      regedit /e lanmanworkstation_configuration_backup.reg HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation

    2. Save the following script to a file with a .REG extension (e.g., Disable_lanmanworkstation.reg):

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation]
      "Start"=dword:00000004

    3. Run the registry script created in step 2 on the target machine with the following command:

      Regedit /s Disable_lanmanworkstation.reg

    4. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    How to undo the workaround.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog, select lanmanworkstation_configuration_backup.reg, and then click Open.

    Using a managed deployment script:

    Restore the original state by running the following command:

    Regedit /s lanmanworkstation_configuration_backup.reg

FAQ for Remote Administration Protocol Denial of Service Vulnerability - CVE-2012-1850

What is the scope of the vulnerability?
This is a denial of service vulnerability.

What causes the vulnerability?
The vulnerability is caused when Windows networking components fail to properly handle a Remote Administration Protocol (RAP) response.

What is the Remote Administration Protocol?
The Remote Administration Protocol (RAP) handles administrative functions that include tasks such as share maintenance and printer maintenance on LAN Manager servers. For more information, see [MS-RAP]: Remote Administration Protocol Specification.

What is the component affected by the vulnerability?
Netapi32.dll is the component affected by the vulnerability.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause the service to stop responding.

How could an attacker exploit the vulnerability?
A remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted RAP packets to the target system.

What systems are primarily at risk from the vulnerability?
Workstations and servers are primarily at risk from this vulnerability.

What does the update do?
The update addresses the vulnerability by correcting how Windows networking components handle RAP responses.

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.

A remote code execution vulnerability exists in the Windows Print Spooler service that could allow a remote, unauthenticated attacker to execute arbitrary code on an affected system. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.

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

Mitigating Factors for Print Spooler Service Format String Vulnerability - CVE-2012-1851

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:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems connected directly to the Internet have a minimal number of ports exposed.

Workarounds for Print Spooler Service Format String Vulnerability - CVE-2012-1851

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:

  • Disable the Print Spooler service

    Disabling the Print Spooler service will help protect the affected system from attempts to exploit this vulnerability. To disable the Print Spooler service, follow these steps:

    Interactive method:

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    1. Click Start, click Run, type regedit, and then click OK.

    2. In Registry Editor, expand the following registry location:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    3. Select Print Spooler, and then click the File menu and select Export.

    4. In the Export Registry File dialog, type spooler_configuration_backup.reg and click Save.

    5. Double-click the registry DWORD entry named Start, change its value to 4, and then click OK.

    6. Run the following command at a command prompt running as an administrator:

      sc stop spooler

    Using a managed deployment script:

    1. Create a back-up copy of the registry keys using a managed deployment script with the following command:

      regedit /e spooler_configuration_backup.reg
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\spooler

    2. Create a text file named Disable_spooler.reg with the following contents:

      Windows Registry Editor Version 5.00

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler]
      "Start"=dword:00000004

    3. Run the registry script created in step 2 on the target machine by using the following command:

      Regedit /s Disable_spooler.reg

    4. Run the following command at a command prompt running as an administrator:

      sc stop spooler

    Impact of workaround. Print-related components will not function properly; printing will be disabled.

    How to undo the workaround.

    To undo the workaround if applied using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog select the registry backup file you created (spooler_configuration_backup.reg) and then click Open.

    To undo the workaround if applied using the managed deployment script, run the following command at a command prompt running as an administrator:

    Regedit /s spooler_configuration_backup.reg

FAQ for Print Spooler Service Format String Vulnerability - CVE-2012-1851

What is the scope of the vulnerability?
This is a remote code execution vulnerability.

What causes the vulnerability?
This vulnerability is caused when the Windows Print Spooler fails to handle a specially crafted response.

What is the component affected by the vulnerability?
The Windows Print Spooler service is the component affected by the vulnerability.

What is the Print Spooler service?
The Print Spooler service is an executable file that is installed as a service. The spooler is loaded when the operating system starts, and it continues to run until the operating system is shut down. The Print Spooler service manages the printing process, which includes such tasks as retrieving the location of the correct printer driver, loading that driver, spooling high-level function calls into a print job, and scheduling print jobs. When the tasks for a particular print job are complete, the Print Spooler service passes the job to the print router. For more information, see How Network Printing Works.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user's system with system privileges. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.

How could an attacker exploit the vulnerability?
A remote unauthenticated attacker could exploit the vulnerability by responding to the print spooler's requests with a specially crafted response.

What systems are primarily at risk from the vulnerability?
Workstations and servers are primarily at risk from this vulnerability.

What does the update do?
The update addresses the vulnerability by correcting how the Windows Print Spooler handles specially crafted responses.

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.

Remote Administration Protocol Heap Overflow Vulnerability - CVE-2012-1852

A remote code execution vulnerability exists in the way that Windows networking components handle a specially crafted RAP response. An attacker who successfully exploited this vulnerability could run arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Remote Administration Protocol Heap Overflow Vulnerability - CVE-2012-1852

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:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems connected directly to the Internet have a minimal number of ports exposed.

Workarounds for Remote Administration Protocol Heap Overflow Vulnerability - CVE-2012-1852

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:

  • Disable the LanmanWorkstation service

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    We recommend that you back up the registry before you edit it.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.

    2. In Registry Editor, expand the following registry location:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    3. Select LanmanWorkstation, and then click the File menu and select Export.

    4. In the Export Registry File dialog, type lanmanworkstation_configuration_backup.reg, and then click Save.

    5. Double-click the Start registry entry, change the Valuedata field to 4, and then click OK.

    6. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    Using a managed deployment script:

    1. Make a backup copy of the registry keys using a managed deployment script with the following command:

      regedit /e lanmanworkstation_configuration_backup.reg HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation

    2. Save the following script to a file with a .REG extension (e.g., Disable_lanmanworkstation.reg):

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation]
      "Start"=dword:00000004

    3. Run the registry script created in step 2 on the target machine with the following command:

      Regedit /s Disable_lanmanworkstation.reg

    4. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    How to undo the workaround.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog, select lanmanworkstation_configuration_backup.reg, and then click Open.

    Using a managed deployment script:

    Restore the original state by running the following command:

    Regedit /s lanmanworkstation_configuration_backup.reg

FAQ for Remote Administration Protocol Heap Overflow Vulnerability - CVE-2012-1852

What is the scope of the vulnerability?
This is a remote code execution vulnerability.

What causes the vulnerability?
The vulnerability is caused when Windows networking components fail to properly handle a Remote Administration Protocol (RAP) response.

What is the Remote Administration Protocol?
The Remote Administration Protocol (RAP) handles administrative functions that include tasks such as share maintenance and printer maintenance on LAN Manager servers. For more information, see [MS-RAP]: Remote Administration Protocol Specification.

What is the component affected by the vulnerability?
Netapi32.dll is the component affected by the vulnerability.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user's system with system privileges. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.

How could an attacker exploit the vulnerability?
A remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted RAP packets to the target system.

What systems are primarily at risk from the vulnerability?
Workstations are primarily at risk from this vulnerability.

What does the update do?
The update addresses the vulnerability by correcting how Windows networking components handle RAP responses.

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.

Remote Administration Protocol Stack Overflow Vulnerability - CVE-2012-1853

A remote code execution vulnerability exists in the way that Windows networking components handle specially crafted RAP responses. An attacker who successfully exploited this vulnerability could run arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Remote Administration Protocol Stack Overflow Vulnerability - CVE-2012-1853

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:

  • Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems connected directly to the Internet have a minimal number of ports exposed.

Workarounds for Remote Administration Protocol Stack Overflow Vulnerability - CVE-2012-1853

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:

  • Disable the LanmanWorkstation service

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    We recommend that you back up the registry before you edit it.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.

    2. In Registry Editor, expand the following registry location:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    3. Select LanmanWorkstation, and then click the File menu and select Export.

    4. In the Export Registry File dialog, type lanmanworkstation_configuration_backup.reg, and then click Save.

    5. Double-click the Start registry entry, change the Valuedata field to 4, and then click OK.

    6. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    Using a managed deployment script:

    1. Make a backup copy of the registry keys using a managed deployment script with the following command:

      regedit /e lanmanworkstation_configuration_backup.reg
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation

    2. Save the following script to a file with a .REG extension (e.g., Disable_lanmanworkstation.reg):

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanworkstation]
      "Start"=dword:00000004

    3. Run the registry script created in step 2 on the target machine with the following command:

      Regedit /s Disable_lanmanworkstation.reg

    4. Run the following command at a command prompt running as an administrator:

      sc stop lanmanworkstation

    How to undo the workaround.

    Using the interactive method:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog, select lanmanworkstation_configuration_backup.reg, and then click Open.

    Using a managed deployment script:

    Restore the original state by running the following command:

    Regedit /s lanmanworkstation_configuration_backup.reg

FAQ for Remote Administration Protocol Stack Overflow Vulnerability - CVE-2012-1853

What is the scope of the vulnerability?
This is a remote code execution vulnerability.

What causes the vulnerability?
The vulnerability is caused when Windows networking components fail to properly handle a Remote Administration Protocol (RAP) response.

What is the Remote Administration Protocol?
The Remote Administration Protocol (RAP) handles administrative functions that include tasks such as share maintenance and printer maintenance on LAN Manager servers. For more information, see [MS-RAP]: Remote Administration Protocol Specification.

What is the component affected by the vulnerability?
Browser.dll is the component affected by the vulnerability?

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user's system with system privileges. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts.

How could an attacker exploit the vulnerability?
A remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted RAP packets to the target system.

What systems are primarily at risk from the vulnerability?
Workstations are primarily at risk from this vulnerability.

What does the update do?
The update addresses the vulnerability by correcting how Windows networking components handle RAP responses.

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

Security Central

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS12-001"), you can add all the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA
Windows XP Service Pack 3 Yes
Windows XP Professional x64 Edition Service Pack 2 Yes
Windows Server 2003 Service Pack 2 Yes
Windows Server 2003 x64 Edition Service Pack 2 Yes
Windows Server 2003 with SP2 for Itanium-based Systems Yes
Windows Vista Service Pack 2 Yes
Windows Vista x64 Edition Service Pack 2 Yes
Windows Server 2008 for 32-bit Systems Service Pack 2 Yes
Windows Server 2008 for x64-based Systems Service Pack 2 Yes
Windows Server 2008 for Itanium-based Systems Service Pack 2 Yes
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 Yes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 Yes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 Yes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Yes

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software SMS 2003 with ITMU System Center Configuration Manager
Windows XP Service Pack 3 Yes Yes
Windows XP Professional x64 Edition Service Pack 2 Yes Yes
Windows Server 2003 Service Pack 2 Yes Yes
Windows Server 2003 x64 Edition Service Pack 2 Yes Yes
Windows Server 2003 with SP2 for Itanium-based Systems Yes Yes
Windows Vista Service Pack 2 Yes Yes
Windows Vista x64 Edition Service Pack 2 Yes Yes
Windows Server 2008 for 32-bit Systems Service Pack 2 Yes Yes
Windows Server 2008 for x64-based Systems Service Pack 2 Yes Yes
Windows Server 2008 for Itanium-based Systems Service Pack 2 Yes Yes
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 Yes Yes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 Yes Yes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 Yes Yes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Yes Yes

Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see System Center.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Security Update Deployment

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment  
Installing without user intervention For Windows XP Service Pack 3:\ WindowsXP-KB2705219-v2-x86-ENU.exe /quiet\ WindowsXP-KB2712808-x86-enu.exe /quiet
For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2705219-v2-x64-ENU.exe /quiet\ WindowsServer2003.WindowsXP-KB2712808-x64-enu.exe /quiet
Installing without restarting For Windows XP Service Pack 3:\ WindowsXP-KB2705219-v2-x86-ENU.exe /norestart\ WindowsXP-KB2712808-x86-enu.exe /norestart
For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2705219-v2-x64-ENU.exe /norestart\ WindowsServer2003.WindowsXP-KB2712808-x64-enu.exe /norestart
Update log file KB2705219-v2.log\ KB2712808.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable
Removal Information Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the following folders:\ %Windir%$NTUninstallKB2705219-v2$\Spuninst\ %Windir%$NTUninstallKB2712808$\Spuninst
File Information See Microsoft Knowledge Base Article 2705219\ See Microsoft Knowledge Base Article 2712808
Registry Key Verification For all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2705219-v2\Filelist\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2712808\Filelist
For all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2705219-v2\Filelist\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2712808\Filelist

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

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, see Microsoft Knowledge Base Article 832475.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch Description
/help Displays the command-line options.
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed.
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem Overwrites OEM files without prompting.
/nobackup Does not back up files needed for uninstall.
/forceappsclose Forces other programs to close when the computer shuts down.
/log:path Allows the redirection of installation log files.
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program.
/ER Enables extended error reporting.
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Switch Description
/help Displays the command-line options.
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose Forces other programs to close when the computer shuts down.
/log:path Allows the redirection of installation log files.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification
    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2705219-v2-x86-ENU.exe /quiet WindowsServer2003-KB2712808-x86-enu.exe /quiet
  For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2705219-v2-x64-ENU.exe /quiet WindowsServer2003.WindowsXP-KB2712808-x64-enu.exe /quiet
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2705219-v2-ia64-ENU.exe /quiet WindowsServer2003-KB2712808-ia64-enu.exe /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2705219-v2-x86-ENU.exe /norestart WindowsServer2003-KB2712808-x86-enu.exe /norestart
  For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2705219-v2-x64-ENU.exe /norestart WindowsServer2003.WindowsXP-KB2712808-x64-enu.exe /norestart
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2705219-v2-ia64-ENU.exe /norestart WindowsServer2003-KB2712808-ia64-enu.exe /norestart
Update log file KB2705219-v2.log KB2712808.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the following folders: %Windir%\$NTUninstallKB2705219-v2$\Spuninst %Windir%\$NTUninstallKB2712808$\Spuninst
File Information See Microsoft Knowledge Base Article 2705219 See Microsoft Knowledge Base Article 2712808
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2705219-v2\Filelist HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2712808\Filelist

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

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the installer, see Microsoft Knowledge Base Article 832475.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch Description
/help Displays the command-line options.
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed.
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem Overwrites OEM files without prompting.
/nobackup Does not back up files needed for uninstall.
/forceappsclose Forces other programs to close when the computer shuts down.
/log:path Allows the redirection of installation log files.
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program.
/ER Enables extended error reporting.
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Switch Description
/help Displays the command-line options.
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed.
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Displays a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose Forces other programs to close when the computer shuts down.
/log:path Allows the redirection of installation log files.

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification
    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment  
Installing without user intervention For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2705219-v2-x86.msu /quiet\ Windows6.0-KB2712808-x86.msu /quiet
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2705219-v2-x64.msu /quiet\ Windows6.0-KB2712808-x64.msu /quiet
Installing without restarting For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2705219-v2-x86.msu /quiet /norestart\ Windows6.0-KB2712808-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2705219-v2-x64.msu /quiet /norestart\ Windows6.0-KB2712808-x64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
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 2705219\ See Microsoft Knowledge Base Article 2712808
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment  
Installing without user intervention For all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-x86.msu /quiet\ Windows6.0-KB2712808-x86.msu /quiet
For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-x64.msu /quiet\ Windows6.0-KB2712808-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-ia64.msu /quiet\ Windows6.0-KB2712808-ia64.msu /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-x86.msu /quiet /norestart\ Windows6.0-KB2712808-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-x64.msu /quiet /norestart\ Windows6.0-KB2712808-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2705219-v2-ia64.msu /quiet /norestart\ Windows6.0-KB2712808-ia64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
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 2705219\ See Microsoft Knowledge Base Article 2712808
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows 7 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment  
Installing without user intervention For all supported 32-bit editions of Windows 7:\ Windows6.1-KB2705219-v2-x86.msu /quiet\ Windows6.1-KB2712808-x86.msu /quiet
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2705219-v2-x64.msu /quiet\ Windows6.1-KB2712808-x64.msu /quiet
Installing without restarting For all supported 32-bit editions of Windows 7:\ Windows6.1-KB2705219-v2-x86.msu /quiet /norestart\ Windows6.1-KB2712808-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2705219-v2-x64.msu /quiet /norestart\ Windows6.1-KB2712808-x64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
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 2705219\ See Microsoft Knowledge Base Article 2712808
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds> When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name> Enables logging to specified file.
/extract:<destination> Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number> Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 R2 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment  
Installing without user intervention For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2705219-v2-x64.msu /quiet\ Windows6.1-KB2712808-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2705219-v2-ia64.msu /quiet\ Windows6.1-KB2712808-ia64.msu /quiet
Installing without restarting For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2705219-v2-x64.msu /quiet /norestart\ Windows6.1-KB2712808-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2705219-v2-ia64.msu /quiet /norestart\ Windows6.1-KB2712808-ia64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement  
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
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 2705219\ See Microsoft Knowledge Base Article 2712808
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches

Switch Description
/?, /h, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds> When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name> Enables logging to specified file.
/extract:<destination> Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number> Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
      Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Yamata Li of Palo Alto Networks for reporting the Remote Administration Protocol Denial of Service Vulnerability (CVE-2012-1850)
  • Yamata Li of Palo Alto Networks for reporting the Print Spooler Service Format String Vulnerability (CVE-2012-1851)
  • Yamata Li of Palo Alto Networks for reporting the Remote Administration Protocol Heap Overflow Vulnerability (CVE-2012-1852)
  • Yamata Li of Palo Alto Networks for reporting the Remote Administration Protocol Stack Overflow Vulnerability (CVE-2012-1853)

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 (August 14, 2012): Bulletin published.
  • V1.1 (August 15, 2012): Clarified that the KB2712808 update is only offered to systems running a Server Core installation option of Windows Server 2008 R2 when the Printing-ServerCore-Role setting is enabled.
  • V2.0 (October 9, 2012): Revised bulletin to rerelease the KB2705219 update for Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. Customers using Windows XP and Windows Server 2003 do not need to apply the rereleased update packages to avoid an issue with digital certificates described in Microsoft Security Advisory 2749655. Customers using Windows Vista, Windows 7, and Windows Server 2008 need to apply the rereleased update packages to avoid an issue with digital certificates described in Microsoft Security Advisory 2749655.
  • V2.1 (October 10, 2012): For the rereleased KB2705219 update, added an FAQ entry to provide deployment guidance. See the update FAQ for details.
  • V2.2 (July 9, 2013): Bulletin revised to announce a detection change in the Windows Vista packages for the 2705219 update to correct a Windows Update reoffering issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.

Built at 2014-04-18T13:49:36Z-07:00