Q-272: Vulnerability in HTML Help

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

General Information

Executive Summary

Executive Summary:

This update resolves a newly discovered, publicly reported vulnerability as well as additional issues discovered through internal investigations. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

On vulnerable versions of Windows, if a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of the client workstation. 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.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers	Impact of Vulnerability	Windows 2000	Windows XP Service Pack 1	Windows XP Service Pack 2	Windows Server 2003	Windows Server 2003 Service Pack 1
Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357	Remote Code Execution	Critical	Critical	Critical	Moderate	Moderate

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates some of the vulnerabilities. See the FAQ section for this security update for more information about Internet Explorer Enhanced Security Configuration.

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

•	The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
•	The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
•	The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
•	The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.

Top of section

Frequently Asked Questions (FAQ) Related to This Security Update

What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.

Bulletin ID	Windows 2000	Windows XP Service Pack 1	Windows XP Service Pack 2	Windows Server 2003	Windows Server 2003 Service Pack 1
MS05-001	Replaced	Replaced	Replaced	Replaced	Replaced

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 922616 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 922616.

Extended security update support for Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems, what should I do?
Windows 98, Windows 98 Second Edition, or Windows Millennium Edition has reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

What is the Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:

•	Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.
•	Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
•	Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
•	Multimedia content is disabled. This setting prevents music, animations, and video clips from running.

Can I enable trusted HTML Help content outside the Local Machine zone?
Yes. You can enable HTML Help content outside the Local Machine zone. You can allow specific sites or security zones to render HTML Help content. To do this, create either or both of the following registry keys.

Warning When you do this, be very selective and allow only sites or security zones that you trust.

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.

To allow specific sites to render HTML Help content:

1.	Click Start, click Run, type Regedit in the Open box, and then click OK.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x Note If this registry subkey does not exist, create it.
3.	On the Edit menu, point to New, and then click Key.
4.	Type HHRestrictions, and then press ENTER.
5.	Right-click the HHRestrictions subkey, point to New, and then click String Value.
6.	Type UrlAllowList, and then press ENTER.
7.	Right-click the UrlAllowList value and then click Modify.
8.	Add URL prefixes as a semi-colon separated list into the Value Data field, and then press ENTER. For example, “http://www.wingtiptoys.com/help/helpdocuments;http://myintranetapplication/help/helpfiles” (without the quotation marks). Note The Value Data field of this registry value is by default blank.

To allow all sites in a specific zone to render HTML Help content:

1.	Click Start, click Run, type Regedit in the Open box, and then click OK.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x Note If this registry subkey does not exist, create it.
3.	On the Edit menu, point to New, and then click Key.
4.	Type HHRestrictions, and then press ENTER.
5.	Right-click the HHRestrictions subkey, point to New, and then click DWORD Value.
6.	Type MaxAllowedZone, and then press ENTER.
7.	Right-click the MaxAllowedZone value and then click Modify.
8.	Change the Value Data field to a number between 0 and 4, and then press ENTER.

Note The Value Data field of this registry value is by default set to 0 (zero). See the following table that outlines how different values are interpreted.

MaxAllowedZone	Local Machine zone	Local intranet zone	Trusted sites zone	Internet zone	Restricted sites zone
0	Allowed	Blocked	Blocked	Blocked	Blocked
1	Allowed	Allowed	Blocked	Blocked	Blocked
2	Allowed	Allowed	Allowed	Blocked	Blocked
3	Allowed	Allowed	Allowed	Allowed	Blocked
4	Allowed	Allowed	Allowed	Allowed	Allowed

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.

Software	MBSA 1.2.1	MBSA 2.0
Microsoft Windows 2000 Service Pack 4	Yes	Yes
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2	Yes	Yes
Microsoft Windows XP Professional x64 Edition	No	Yes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1	Yes	Yes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems	No	Yes
Microsoft Windows Server 2003 x64 Edition family	No	Yes

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

For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.

Software	SMS 2.0	SMS 2003
Microsoft Windows 2000 Service Pack 4	Yes	Yes
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2	Yes	Yes
Microsoft Windows XP Professional x64 Edition	No	Yes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1	Yes	Yes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems	No	Yes
Microsoft Windows Server 2003 x64 Edition family	No	Yes

SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to software that MBSA does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates 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 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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

Top of section

Vulnerability Details

Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357

A vulnerability exists in the HTML Help ActiveX control that could allow remote code execution on an affected system. An attacker could exploit the vulnerability by constructing a malicious Web page that could potentially allow remote code execution if a user visited that page. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357:

•

In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability (An attacker could also attempt to compromise a Web site to have it serve up a Web page with malicious content to attempt to exploit this vulnerability.). An attacker would have no way to force users to visit a Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site or to a site that has been compromised by the attacker.

•

An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.

•

By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 2000 opens HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could attempt to exploit this vulnerability.

The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

•	Install the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.
•	Use Microsoft Outlook 2000 with the Microsoft Outlook E-mail Security Update installed.
•	Use Microsoft Outlook Express 6 or later or Microsoft Outlook 2000 Service Pack 2 or later in their default configuration.

•

By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability. See the FAQ section for this security update for more information about Internet Explorer Enhanced Security Configuration.

Top of section

Workarounds for Buffer Overrun in HTML Help Vulnerability- CVE-2006-3357:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

•

Disable the HTML Help ActiveX control from running within Internet Explorer 6 for Windows XP Service Pack 2.

You can help protect against this vulnerability by changing your settings within Internet Explorer to disable the ActiveX control hhtctrl.ocx from running.

To disable the HTML Help ActiveX control in Microsoft Internet Explorer:

1.	On the Internet Explorer Tools menu, click Manage Add-ons.
2.	Locate and click on “HHCTRL Object”.
3.	To disable the add-on, click Disable and then click OK.

Impact of Workaround: Disabling the HTML Help ActiveX control prevents Internet Explorer from instantiating the control. This configuration causes program compatibility issues. Some examples of such issues are:

•	In Help and Support Center, the Index feature no longer works.
•	In HTML Help, features such as Related Topics and Shortcuts no longer work.

Features that are provided by the HTML Help control in Enterprise intranet programs no longer work.

•

Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX controls and active scripting in the Internet zone and in the Local intranet zone.

You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls and active scripting. You can do this by setting your browser security to High.

To raise the browsing security level in Microsoft Internet Explorer:

1.	On the Internet Explorer Tools menu, click Internet Options.
2.	In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
3.	Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

Note If no slider is visible, click Default Level, and then move the slider to High.

Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the high security setting.

Alternatively, you can change you settings to prompt before running ActiveX controls only by following these steps:

1.	In Internet Explorer, click Internet Options on the Tools menu.
2.	Click the Security tab.
3.	Click Internet, and then click Custom Level.
4.	Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.
5.	In the Scripting section, under Active Scripting, click Prompt, and then click OK.
6.	Click Local intranet, and then click Custom Level.
7.	Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.
8.	In the Scripting section, under Active Scripting, click Prompt.
9.	Click OK two times to return to Internet Explorer.

Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the "Restrict Web sites to only your trusted Web sites" workaround.

•

Restrict Web sites to only your trusted Web sites.

After you set Internet Explorer to require a prompt before it runs ActiveX controls and active scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to Internet Explorer's Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

To do this, follow these steps:

1.	In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
2.	In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
3.	If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
4.	In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
5.	Repeat these steps for each site that you want to add to the zone.
6.	Click OK two times to accept the changes and return to Internet Explorer.

Add any sites that you trust not to take malicious action on your computer. One in particular that you may want to add is "*.windowsupdate.microsoft.com" (without the quotation marks). This is the site that will host the update, and it requires using an ActiveX control to install the update.

•

Temporarily disable the HTML Help ActiveX control from running in Internet Explorer

You can help protect against this vulnerability by temporarily disabling the HTML Help ActiveX control from running in Internet Explorer by setting the kill bit for the control.

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.

The CLSID for an ActiveX control is a GUID for that control. You can prevent an ActiveX control from running in Internet Explorer by setting the kill bit so that the control is never called by Internet Explorer. The kill bit is a specific value for the Compatibility Flags DWORD value for the ActiveX control in the registry.

The CLSID for the HTML Help ActiveX control is {52a2aaae-085d-4187-97ea-8c30db990436}

For detailed steps about stopping an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps and create a Compatibility Flags value in the registry to prevent the HTML Help ActiveX control from being instantiated in Internet Explorer

Note If you use this workaround you must reset this registry change by removing the same Compatibility Flags registry value. You should do this after you have applied this security update to regain normal functionality supplied by the HTML Help ActiveX control.

•	In Help and Support Center, the Index feature no longer works.
•	In HTML Help, features such as Related Topics and Shortcuts no longer work.

Features that are provided by the HTML Help control in Enterprise intranet programs no longer work.

Top of section

FAQ for Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357:

What is the scope of the vulnerability?
This is a vulnerability that could allow remote code execution. If a user is logged on with administrative 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 with full privileges. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.

What causes the vulnerability?
A vulnerability in a string buffer, within the HTML Help ActiveX control.

What is HTML Help?
Microsoft HTML Help is the standard help system for the Windows platform. The HTML Help ActiveX control is a program that is used to insert help navigation and secondary window functionality into an HTML file. For more information about the HTML Help ActiveX control, see the product documentation.

What are Internet Explorer security zones?
Internet Explorer security zones are part of a system that divides online content into categories or zones that are based on the trustworthiness of the content. Specific Web domains can be assigned to a zone, depending on how much you trust the content of each domain. The zone then restricts the capabilities of the Web content, based on the zone's policy. By default, most Internet domains are treated as part of the Internet zone. By default, the policy of the Internet zone prevents scripts and other active code from accessing resources on the local system.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run malicious code on a users system. This could allow an attacker to take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by creating a malicious Web page and persuading the user to visit the page. An attacker could also attempt to compromise a Web site to have it serve up a Web page with malicious content to try to exploit this vulnerability. When the user has visited the page, the attacker could access information from other Web sites, access local files on the system, or cause malicious script to run as the locally logged on user.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user view Web sites for malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as users’ workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to visit Web sites, such as most server systems, are at a reduced risk.

Could the vulnerability be exploited over the Internet?
An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.

What does the update do?
The update removes the vulnerability by correcting the issue within the affected string buffer.

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 CAN-2006-3357.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. When the security bulletin was released, Microsoft had not received information that this vulnerability was being exploited

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2006-3357.

Top of section

Security Update Information

Affected Software:

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

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.

Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.

Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation 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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays 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	Display 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 uninstallation.
/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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003- kb922616-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB922616.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb922616-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB922616$\Spuninst folder.

Supported Spuninst.exe 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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays 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	Display 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.

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:

File Name	Version	Date	Time	Size	CPU	Folder
Hhctrl.ocx	5.2.3790.558	11-Jul-2006	13:14	519,168	x86	RTMGDR
Hhctrl.ocx	5.2.3790.558	11-Jul-2006	13:02	519,168	x86	RTMQFE
Hhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:16	546,304	x86	SP1GDR
Hhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:27	546,304	x86	SP1QFE

Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:

File Name	Version	Date	Time	Size	CPU	Folder
Hhctrl.ocx	5.2.3790.558	11-Jul-2006	13:45	1,550,848	IA-64	RTMGDR
Whhctrl.ocx	5.2.3790.558	11-Jul-2006	13:45	519,168	x86	RTMGDR\WOW
Hhctrl.ocx	5.2.3790.558	11-Jul-2006	13:45	1,550,848	IA-64	RTMQFE
Whhctrl.ocx	5.2.3790.558	11-Jul-2006	13:45	519,168	x86	RTMQFE\WOW
Hhctrl.ocx	5.2.3790.2744	12-Jul-2006	12:02	1,722,368	IA-64	SP1GDR
Whhctrl.ocx	5.2.3790.2744	12-Jul-2006	12:02	546,304	x86	SP1GDR\WOW
Hhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	1,722,368	IA-64	SP1QFE
Whhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	546,304	x86	SP1QFE\WOW

Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:

File Name	Version	Date	Time	Size	CPU	Folder
Hhctrl.ocx	5.2.3790.2744	12-Jul-2006	12:02	858,624	x64	SP1GDR
Whhctrl.ocx	5.2.3790.2744	12-Jul-2006	12:02	546,304	x86	SP1GDR\WOW
Hhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	858,624	x64	SP1QFE
Whhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	546,304	x86	SP1QFE\WOW

Notes When you install these security updates, the installer checks to see if 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 this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

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

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 can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

•

File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 version of the operating system or programs installed, 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 computer 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 following registry keys.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB922616\

Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the security update into the Windows installation source files.

Top of section

Windows XP (all versions)

Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation 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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays 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	Display 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 uninstallation.
/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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:

Windowsxp- kb922616-x86-enu /quiet

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:

Windowsxp- kb922616-x86-enu /norestart

Restart Requirement

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB922616$\Spuninst folder.

Supported Spuninst.exe 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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays 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	Display 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.

File Information

Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

File Name	Version	Date	Time	Size	CPU	Folder
Hhctrl.ocx	5.2.3790.558	14-Jul-2006	15:35	519,168	x86	SP1QFE
Hhctrl.ocx	5.2.3790.2744	14-Jul-2006	15:25	546,304	x86	SP2GDR
Hhctrl.ocx	5.2.3790.2744	14-Jul-2006	15:37	546,304	x86	SP2QFE

Windows XP Professional x64:

Hhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	858,624	x64	SP1QFE
Whhctrl.ocx	5.2.3790.2744	11-Jul-2006	13:45	546,304	x86	SP1QFE\WOW

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

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

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer

•

File Version Verification


PROBLEM:	A vulnerability exists in the HTML Help ActiveX Control.
PLATFORM:	• Microsoft Windows 2000 Service Pack 4 • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 • Microsoft Windows XP Professional x64 Edition • Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems • Microsoft Windows Server 2003 x64 Edition HP-UX B.11.00, B.11.11, B.11.23
DAMAGE:	Remote code execution.
SOLUTION:	Upgrade to the appropriate version.

VULNERABILITY ASSESSMENT:	The risk is HIGH. Could allow remote code execution on an affected system.

LINKS:
CIAC BULLETIN:	http://www.ciac.org/ciac/bulletins/q-272.shtml
ORIGINAL BULLETIN:	Microsoft Security Bulletin MS06-046 (922616) http://www.microsoft.com/technet/security/bulletin/ms06-046.mspx Visit Hewlett-Packard Subscription Service for: HPSBUX02164 SSRT061265 Visit Hewlett-Packard Subscription Service for: HPSBUX02172 SSRT061269 Visit Hewlett-Packard Subscription Service for: HPSBUX02145 SSRT061202 rev. 2
CVE:	CVE-2006-3357

INFORMATION BULLETIN

Q-272: Vulnerability in HTML Help

[Microsoft Security Bulletin MS06-046 (922616)]

Microsoft Security Bulletin MS06-046

Vulnerability in HTML Help Could Allow Remote Code Execution (922616)

Summary

General Information

Executive Summary

Frequently Asked Questions (FAQ) Related to This Security Update

Vulnerability Details

Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357

Mitigating Factors for Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357:

Workarounds for Buffer Overrun in HTML Help Vulnerability- CVE-2006-3357:

FAQ for Buffer Overrun in HTML Help Vulnerability - CVE-2006-3357:

Security Update Information

Windows Server 2003 (all versions)

Windows XP (all versions)

•	Microsoft Windows 2000 Service Pack 4 — Download the update
•	Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 — Download the update
•	Microsoft Windows XP Professional x64 Edition — Download the update
•	Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 — Download the update
•	Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems — Download the update
•	Microsoft Windows Server 2003 x64 Edition — Download the update