Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS11-024 - Important

Vulnerabilities in Windows Fax Cover Page Editor Could Allow Remote Code Execution (2527308)

Published: April 12, 2011 | Updated: April 27, 2011

Version: 1.2

General Information

Executive Summary

This security update resolves two publicly disclosed vulnerabilities in Microsoft Windows. The vulnerabilities could allow remote code execution if a user opened a specially crafted fax cover page file (.cov) using the Windows Fax Cover Page Editor. An attacker who successfully exploited either of these vulnerabilities could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

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

The security update addresses the vulnerabilities by correcting the manner in which the Windows Fax Page Editor parses fax cover page files and manages objects within fax cover page files. 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. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

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

Known Issues. Microsoft Knowledge Base Article 2527308 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

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, visit Microsoft Support Lifecycle.

Affected Software

Operating SystemMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Windows XP Service Pack 3 
(KB2491683)

Windows XP Service Pack 3 
(KB2506212)
Remote Code ExecutionImportantNone
Windows XP Professional x64 Edition Service Pack 2 
(KB2491683)

Windows XP Professional x64 Edition Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2003 Service Pack 2 
(KB2491683)

Windows Server 2003 Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2003 x64 Edition Service Pack 2 
(KB2491683)

Windows Server 2003 x64 Edition Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2003 with SP2 for Itanium-based Systems 
(KB2491683)

Windows Server 2003 with SP2 for Itanium-based Systems 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 
(KB2491683)

Windows Vista Service Pack 1 and Windows Vista Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 
(KB2491683)

Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** 
(KB2491683)

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** 
(KB2491683)

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 
(KB2506212)
Remote Code ExecutionImportantNone
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 
(KB2491683)

Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 
(KB2506212)
Remote Code ExecutionImportantNone
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 
(KB2491683)

Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1** 
(KB2491683)

Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1
(KB2506212)
Remote Code ExecutionImportantNone
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 
(KB2506212)
Remote Code ExecutionImportantNone

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

Why was this bulletin revised on April 27, 2011? 
Microsoft revised this bulletin to add CVE-2010-4701 to the vulnerabilities addressed by this update. This is an informational change only. There were no changes to the security update files or detection logic. Customers who have successfully applied this update do not need to take any further action.

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.

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. Instead of having to install several updates that are almost the same, customers need to install this update only.

Why does this bulletin contain two updates for most affected operating systems? 
This bulletin contains two updates, identified by package KB number, for most supported editions of Microsoft Windows as specified in the Affected Software table. The two updates are necessary for most affected operating systems because the modifications that are required to address the vulnerabilities are located in separate components.

There are two updates listed for the version of Microsoft Windows installed on my system. Do I need to install both updates? 
Yes. Customers should apply all updates offered for the operating system 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 an affected version of Microsoft Windows. Why is the KB2491683 update not offered? 
The KB2491683 update only applies if the vulnerable Fax Cover Page Editor (fxscover.exe) application is installed. Systems that do not have the vulnerable Fax Cover Page Editor application installed will not be offered the KB2491683 update.

In all supported editions of Windows XP and Windows Server 2003, the Windows Fax Cover Page Editor is only available if the optional Fax Services component is enabled. The Fax Services component is not installed by default on these operating systems.

The Fax Cover Page Editor application is not available in supported versions of Windows Vista Home Basic and Windows Vista Home Premium. In supported versions of Windows Vista Enterprise Edition, the Windows Fax Cover Page Editor is available as an optional component.

In supported versions of Windows Vista Business Edition and Windows Vista Ultimate Edition, and in all supported editions of Windows 7, the Windows Fax Cover Page Editor is available by default.

In supported versions of Windows Server 2008 (32-bit and x64-based only) and Windows Server 2008 R2 (x64-based only), the Fax Cover Page Editor is available if the Fax Server role is enabled.

Note The KB2506212 update applies to all affected operating systems regardless of whether or not the Fax Cover Page Editor application is installed.

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, visit the Microsoft Support Lifecycle Web site.

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 Lifecycle Supported Service Packs.

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, visit the Microsoft Worldwide Information Web site, 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

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareFax Cover Page Editor Memory Corruption Vulnerability - CVE-2010-3974Fax Cover Page Use After Free Vulnerability - CVE-2010-4701Aggregate Severity Rating
Windows XP Service Pack 3
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows XP Professional x64 Edition Service Pack 2
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2003 Service Pack 2
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2003 x64 Edition Service Pack 2
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2003 with SP2 for Itanium-based Systems
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2**
(KB2491683)

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*
(KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2**
(KB2491683)

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*
(KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
(KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
(KB2491683 and KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1**
(KB2491683)

Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1*
(KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(KB2506212)
Important 
Remote Code Execution
Important 
Remote Code Execution
Important

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

A remote code execution vulnerability exists in the way that the Windows Fax Cover Page Editor improperly parses specially crafted fax cover pages. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

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

Mitigating Factors for Fax Cover Page Editor Memory Corruption Vulnerability - CVE-2010-3974

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:

  • On all supported editions of Windows XP and Windows Server 2003, the Windows Fax Cover Page Editor is not installed by default. For the Windows Fax Cover Page Editor to be available, the Fax Services component of these operating systems would need to be enabled.
  • On all supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, by default, the affected file type (.cov) is not registered to any program. For an attack to be successful, a user would first need to open the Windows Fax Cover Page Editor and then open a specially crafted .cov file.
  • The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.

Workarounds for Fax Cover Page Editor Memory Corruption Vulnerability - CVE-2010-3974

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:

  • Remove the Fax Cover Page .COV file association on Windows XP and Windows Server 2003

    If the .cov file type has been associated with the Windows Fax Cover Page Editor, removing the file association prevents the file from being automatically opened.

    Note 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 the Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    To remove the fax cover page (.cov) file association, perform the following steps:

    Using the interactive method

    1. Click Start, click Run, type regedit, and then click OK.
    2. Expand HKEY_CLASSES_ROOT, click on .COV, and then click the File menu and select Export.
    3. In the Export Registry File dialog box, type Cover_Page_Backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    4. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry value, click Yes.

    Using a managed deployment script

    1. Make a backup copy of the registry key using the following command:

      Regedit.exe /e cover_page_backup.reg HKEY_CLASSES_ROOT\.COV
    2. Save the following to a file with a .REG extension (e.g. Delete_Cover_Page_Assoc.reg):

      Windows Registry Editor Version 5.00

      [-HKEY_CLASSES_ROOT\.COV]
    3. Run the registry script created in the previous step with the following command:

      Regedit.exe /s delete_cover_page.reg

    Impact of workaround. This workaround removes the .COV file association. Double-clicking a COV file will no longer launch Windows Fax Cover Page Editor.

    How to undo the workaround.

    Using the interactive method

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select Cover_Page_Backup.reg and click Open.

    Using a managed deployment script

    Restore the original state by running the following command:

    Regedit.exe /s cover_page_backup.reg

FAQ for Fax Cover Page Editor Memory Corruption Vulnerability - CVE-2010-3974

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. 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 with full user rights.

What causes the vulnerability? 
The vulnerability is caused when the Windows Fax Cover Page Editor does not properly parse a specially crafted fax cover page.

What is the Windows Fax Cover Page Editor? 
The Fax Cover Page Editor (fxscover.exe) application can be used to create and edit fax cover pages.

In all supported editions of Windows XP and Windows Server 2003, the Windows Fax Cover Page Editor is only available if the optional Fax Services component is enabled. The Fax Services component is not installed by default on these operating systems. For information about enabling the Fax Services component of Microsoft Windows XP, see Microsoft Knowledge Base Article 306550.

In supported versions of Windows Vista Enterprise Edition, the Windows Fax Cover Page Editor is available as an optional component. In supported versions of Windows Vista Business Edition and Windows Vista Ultimate Edition, and in all supported editions of Windows 7, the Windows Fax Cover Page Editor is available by default. In supported versions of Windows Server 2008 (32-bit and x64-based only) and Windows Server 2008 R2 (x64-based only), the Fax Cover Page Editor is available if the Fax Server role is enabled. Typically, on these operating systems, the Windows Cover Page Editor is launched from within the Windows Fax and Scan application or from the Fax Service Manager when a user creates or edits a fax cover page. For more information on creating and editing fax cover pages, see Create or edit a fax cover page and the TechNet article, Managing Cover Pages.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
For an attacker to exploit this vulnerability, a user would need to open a specially crafted fax cover page file (.cov) using the Windows Fax Cover Page Editor.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted fax cover page file (.cov) to the user and by convincing the user to open the file within the Windows Fax Cover Page Editor application.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted fax cover page file (.cov) that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted fax cover page file.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the manner in which the Windows Fax Page Editor parses fax cover page files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2010-3974.

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.

Does applying this security update help protect customers from the code, published publicly, that could attempt to exploit this vulnerability? 
Yes. This security update addresses the vulnerability that potentially could be exploited by using the published proof of concept code. The vulnerability that has been addressed has been assigned Common Vulnerability and Exposure number CVE-2010-3974.

A remote code execution vulnerability exists in the way that the Windows Fax Cover Page Editor manages certain objects when parsing a specially crafted fax cover page. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

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

Mitigating Factors for Fax Cover Page Use After Free Vulnerability - CVE-2010-4701

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:

  • On all supported editions of Windows XP and Windows Server 2003, the Windows Fax Cover Page Editor is not installed by default. For the Windows Fax Cover Page Editor to be available, the Fax Services component of these operating systems would need to be enabled.
  • On all supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, by default, the affected file type (.cov) is not registered to any program. For an attack to be successful, a user would first need to open the Windows Fax Cover Page Editor and then open a specially crafted .cov file.
  • The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.

Workarounds for Fax Cover Page Use After Free Vulnerability - CVE-2010-4701

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:

  • Remove the Fax Cover Page .COV file association on Windows XP and Windows Server 2003

    If the .cov file type has been associated with the Windows Fax Cover Page Editor, removing the file association prevents the file from being automatically opened.

    Note 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 the Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    To remove the fax cover page (.cov) file association, perform the following steps:

    Using the interactive method

    1. Click Start, click Run, type regedit, and then click OK.
    2. Expand HKEY_CLASSES_ROOT, click on .COV, and then click the File menu and select Export.
    3. In the Export Registry File dialog box, type Cover_Page_Backup.reg and click Save.

      Note This will create a backup of this registry key in the My Documents folder by default.
    4. Press the Delete key on the keyboard to delete the registry key. When prompted to delete the registry value, click Yes.

    Using a managed deployment script

    1. Make a backup copy of the registry key using the following command:

      Regedit.exe /e cover_page_backup.reg HKEY_CLASSES_ROOT\.COV
    2. Save the following to a file with a .REG extension (e.g. Delete_Cover_Page_Assoc.reg):

      Windows Registry Editor Version 5.00

      [-HKEY_CLASSES_ROOT\.COV]
    3. Run the registry script created in the previous step with the following command:

      Regedit.exe /s delete_cover_page.reg

    Impact of workaround. This workaround removes the .COV file association. Double-clicking a COV file will no longer launch Windows Fax Cover Page Editor.

    How to undo the workaround.

    Using the interactive method

    1. Click Start, click Run, type Regedit in the Open box, and then click OK.
    2. Click the File menu and select Import.
    3. In the Import Registry File dialog box, select Cover_Page_Backup.reg and click Open.

    Using a managed deployment script

    Restore the original state by running the following command:

    Regedit.exe /s cover_page_backup.reg

FAQ for Fax Cover Page Use After Free Vulnerability - CVE-2010-4701

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. 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 with full user rights.

What causes the vulnerability? 
The vulnerability is caused when the Windows Fax Cover Page Editor does not properly manage certain objects when parsing a specially crafted fax cover page.

What is the Windows Fax Cover Page Editor? 
The Fax Cover Page Editor (fxscover.exe) application can be used to create and edit fax cover pages.

In all supported editions of Windows XP and Windows Server 2003, the Windows Fax Cover Page Editor is only available if the optional Fax Services component is enabled. The Fax Services component is not installed by default on these operating systems. For information about enabling the Fax Services component of Microsoft Windows XP, see Microsoft Knowledge Base Article 306550.

In supported versions of Windows Vista Enterprise Edition, the Windows Fax Cover Page Editor is available as an optional component. In supported versions of Windows Vista Business Edition and Windows Vista Ultimate Edition, and in all supported editions of Windows 7, the Windows Fax Cover Page Editor is available by default. In supported versions of Windows Server 2008 (32-bit and x64-based only) and Windows Server 2008 R2 (x64-based only), the Fax Cover Page Editor is available if the Fax Server role is enabled. Typically, on these operating systems, the Windows Cover Page Editor is launched from within the Windows Fax and Scan application or from the Fax Service Manager when a user creates or edits a fax cover page. For more information on creating and editing fax cover pages, see Create or edit a fax cover page and the TechNet article, Managing Cover Pages.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
For an attacker to exploit this vulnerability, a user would need to open a specially crafted fax cover page file (.cov) using the Windows Fax Cover Page Editor.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted fax cover page file (.cov) to the user and by convincing the user to open the file within the Windows Fax Cover Page Editor application.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted fax cover page file (.cov) that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted fax cover page file.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the manner in which the Windows Fax Page Editor manages objects within fax cover page files.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2010-4701.

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.

Does applying this security update help protect customers from the code, published publicly, that could attempt to exploit this vulnerability? 
Yes. This security update addresses the vulnerability that potentially could be exploited by using the published proof of concept code. The vulnerability that has been addressed has been assigned Common Vulnerability and Exposure number CVE-2010-4701.

Update Information

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 Web site 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, "MS07-036"), you can add all of 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) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

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

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

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit 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.

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Windows XP Service Pack 3YesYesYesYes
Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 2YesYesYesYes
Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2NoNoYesYes
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2NoNoYesYes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2NoNoYesYes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2NoNoYesYes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2NoNoYesYes
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1NoNoYesYes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1NoNoYesYes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1NoNoYesYes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1NoNoYesYes

For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

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 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

For more information about SMS, visit the SMS Web site.

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 Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor Windows XP Service Pack 3:
windowsxp-kb2491683-x86-enu.exe /quiet
windowsxp-kb2506212-x86-enu.exe /quiet
For Windows XP Professional x64 Edition Service Pack 2:
windowsserver2003.windowsxp-kb2491683-x64-enu.exe /quiet
windowsserver2003.windowsxp-kb2506212-x64-enu.exe /quiet
Installing without restartingFor Windows XP Service Pack 3:
windowsxp-kb2491683-x86-enu.exe /norestart
windowsxp-kb2506212-x86-enu.exe /norestart
For Windows XP Professional x64 Edition Service Pack 2:
windowsserver2003.windowsxp-kb2491683-x64-enu.exe /norestart
windowsserver2003.windowsxp-kb2506212-x64-enu.exe /norestart
Update log fileKB2491683.log
KB2506212.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2491683$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212
Registry Key VerificationFor all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2491683\Filelist

For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2506212\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2491683\Filelist

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2506212\Filelist

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security 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.

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.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts 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.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables 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.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows 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 of the 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Server 2003:
windowsserver2003-kb2491683-x86-enu.exe /quiet
windowsserver2003-kb2506212-x86-enu.exe /quiet
For all supported x64-based editions of Windows Server 2003:
windowsserver2003.windowsxp-kb2491683-x64-enu.exe /quiet
windowsserver2003.windowsxp-kb2506212-x64-enu.exe /quiet
For all supported Itanium-based editions of Windows Server 2003:
windowsserver2003-kb2491683-ia64-enu.exe /quiet
windowsserver2003-kb2506212-ia64-enu.exe
Installing without restartingFor all supported 32-bit editions of Windows Server 2003:
windowsserver2003-kb2491683-x86-enu.exe /norestart
windowsserver2003-kb2506212-x86-enu.exe /norestart
For all supported x64-based editions of Windows Server 2003:
windowsserver2003.windowsxp-kb2491683-x64-enu.exe /norestart
windowsserver2003.windowsxp-kb2506212-x64-enu.exe /norestart
For all supported Itanium-based editions of Windows Server 2003:
windowsserver2003-kb2491683-ia64-enu.exe /norestart
windowsserver2003-kb2506212-ia64-enu.exe /norestart
Update log fileKB2491683.log
KB2506212.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2491683$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2491683\Filelist

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

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.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts 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.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables 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.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts 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.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows 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 of the 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Vista:
windows6.0-kb2491683-x86.msu /quiet
windows6.0-kb2506212-x86.msu /quiet
For all supported x64-based editions of Windows Vista:
windows6.0-kb2491683-x64.msu /quiet
windows6.0-kb2506212-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
windows6.0-kb2491683-x86.msu /quiet /norestart
windows6.0-kb2506212-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Vista:
windows6.0-kb2491683-x64.msu /quiet /norestart
windows6.0-kb2506212-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal InformationWUSA.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 InformationSee Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212
Registry Key VerificationNote 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
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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 of the 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows Server 2008:
windows6.0-kb2491683-x86.msu /quiet
windows6.0-kb2506212-x86.msu /quiet
For all supported x64-based editions of Windows Server 2008:
windows6.0-kb2491683-x64.msu /quiet
windows6.0-kb2506212-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008:
windows6.0-kb2506212-ia64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
windows6.0-kb2491683-x86.msu /quiet /norestart
windows6.0-kb2506212-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
windows6.0-kb2491683-x64.msu /quiet /norestart
windows6.0-kb2506212-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
windows6.0-kb2506212-ia64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal InformationWUSA.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 InformationFor all supported 32-bit editions of Windows Server 2008 and for all supported x64-based editions of Windows Server 2008, see Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212.

For all supported Itanium-based editions of Windows Server 2008, see Microsoft Knowledge Base Article 2506212.
Registry Key VerificationNote 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
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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 of the 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported 32-bit editions of Windows 7:
windows6.1-kb2491683-x86.msu /quiet
windows6.1-kb2506212-x86.msu /quiet
For all supported x64-based editions of Windows 7:
windows6.1-kb2491683-x64.msu /quiet
windows6.1-kb2506212-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows 7:
windows6.1-kb2491683-x86.msu /quiet /norestart
windows6.1-kb2506212-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:
windows6.1-kb2491683-x64.msu /quiet /norestart
windows6.1-kb2506212-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal InformationTo 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 InformationSee Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212
Registry Key VerificationNote 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
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen 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 of the 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported x64-based editions of Windows Server 2008 R2:
windows6.1-kb2491683-x64.msu /quiet
windows6.1-kb2506212-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
windows6.1-kb2506212-ia64.msu /quiet
Installing without restartingFor all supported x64-based editions of Windows Server 2008 R2:
windows6.1-kb2491683-x64.msu /quiet /norestart
windows6.1-kb2506212-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
windows6.1-kb2506212-ia64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal InformationTo 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 InformationFor all supported x64-based editions of Windows Server 2008 R2 , see Microsoft Knowledge Base Article 2491683 and Microsoft Knowledge Base Article 2506212.

For all supported Itanium-based editions of Windows Server 2008 R2, see Microsoft Knowledge Base Article 2506212.
Registry Key VerificationNote 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
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen 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 of the 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:

  • Carsten Eiram of Secunia for working with us on the Fax Cover Page Use After Free Vulnerability (CVE-2010-4701)

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 visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

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 (April 12, 2011): Bulletin published.
  • V1.1 (April 20, 2011): Added a link to Microsoft Knowledge Base Article 2527308 under Known Issues in the Executive Summary.
  • V1.2 (April 27, 2011): Corrected the severity table and vulnerability section to add CVE-2010-4701 as a vulnerability addressed by this update. This is an informational change only.

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.