Security Bulletin
Microsoft Security Bulletin MS06-027 - Critical
Vulnerability in Microsoft Word Could Allow Remote Code Execution (917336)
Published: June 13, 2006 | Updated: July 12, 2006
Version: 1.3
Summary
Who Should Read this Document: Customers who use Microsoft Word
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately
Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Office 2000 Service Pack 3
- Microsoft Word 2000 — Download the update (KB917345)
- Microsoft Office XP Service Pack 3
- Microsoft Word 2002 — Download the update (KB917335)
- Microsoft Office 2003 Service Pack 1 or Service Pack 2
- Microsoft Word 2003 — Download the update (KB917334)
- Microsoft Word Viewer 2003 - Download the update (KB917346)
- Microsoft Works Suites:
- Microsoft Works Suite 2000 - Download the update (KB917345) (same as Microsoft Word 2000 update)
- Microsoft Works Suite 2001 - Download the update (KB917345) (same as Microsoft Word 2000 update)
- Microsoft Works Suite 2002 - Download the update (KB917335) (same as the Microsoft Word 2002 update)
- Microsoft Works Suite 2003 - Download the update (KB917335) (same as the Microsoft Word 2002 update)
- Microsoft Works Suite 2004 -Download the update (KB917335) (same as the Microsoft Word 2002 update)
- Microsoft Works Suite 2005 -Download the update (KB917335) (same as the Microsoft Word 2002 update)
- Microsoft Works Suite 2006 -Download the update (KB917335) (same as the Microsoft Word 2002 update)
Non-Affected Software:
- Microsoft Word v. X for Mac
- Microsoft Word 2004 for Mac
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.
General Information
Executive Summary
Executive Summary:
This update resolves a newly discovered, public vulnerability. The vulnerability is documented in this bulletin in the "Vulnerability Details" section of this bulletin.
A remote code execution vulnerability exists in Word using a malformed object pointer. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution.
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 | Microsoft Word 2000 | Microsoft Word 2002 | Microsoft Word 2003 and Word Viewer 2003 |
|---|---|---|---|---|
| Microsoft Word Malformed Object Pointer Vulnerability - CVE-2006-2492 | Remote Code Execution | Critical | Important | Important |
Note The severity ratings for Microsoft Works Suite map to the Microsoft Word versions as follows:
- The Microsoft Works Suite 2000 and 2001 severity rating is the same as the Microsoft Word 2000 severity rating.
- The Microsoft Works Suite 2002, 2003, 2004, 2005, and 2006 severity rating is the same as the Microsoft Word 2002 severity rating.
Frequently Asked Questions (FAQ) Related to this Security Update
What updates does this release replace?
This security update replaces several prior security updates. The security bulletin IDs and affected operating systems are listed in the following table.
| Bulletin ID | Microsoft Word 2000 | Microsoft Word 2002 | Microsoft Word 2003 Service Pack 1 | Microsoft Word Viewer 2003 |
|---|---|---|---|---|
| MS06-012 | Replaced | Replaced | Not Applicable | Not Applicable |
| MS05-023 | Not Applicable | Not Applicable | Replaced | Replaced |
Note All supported versions of Microsoft Works are replaced by MS06-012.
Why does Microsoft Works Suite appear in the Affected Software list?
Microsoft Works Suite appears in the Affected Software list because it includes Microsoft Word. Microsoft Works users should use Office Update to detect and to install the appropriate update.
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.
| Product | MBSA 1.2.1 | MBSA 2.0 |
|---|---|---|
| Microsoft Word 2000 | Yes | No |
| Microsoft Word 2002 | Yes | Yes |
| Microsoft Word 2003 | Yes | Yes |
| Microsoft Word Viewer 2003 | Yes | Yes |
MBSA uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue.
MBSA 2.0 does not support the detection of Office 2000. You should use MBSA 1.2.1 to determine if this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
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 Word 2000 | Yes | No |
| Microsoft Word 2002 | Yes | Yes |
| Microsoft Word 2003 | Yes | Yes |
| Microsoft Word Viewer 2003 | Yes | Yes |
SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs 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.
Vulnerability Details
Microsoft Word Malformed Object Pointer Vulnerability - CVE-2006-2492
A remote code execution vulnerability exists in Word using a malformed object pointer. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution.
If a user is logged on with administrative user rights, 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. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Word Malformed Object Pointer Vulnerability - CVE-2006-2492:
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local 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.
- The vulnerability can not 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.
- On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious 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.
Note While this vulnerability could not be exploited automatically when visiting a Web site using Word 2000, Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Word Code Remote Code Execution Using a Malformed Object Pointer Vulnerability - CVE-2006-2492:
Microsoft has tested the following workarounds. While 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.
Always use Microsoft Word in Safe Mode
Using Word in Safe Mode helps protect the affected system from attempts to exploit this vulnerability.
Step 1 - Disable Outlook Feature to Use Word as the E-mail Editor
For Enterprise Customers
Manual (User Interaction) Enterprise Users follow these steps to disable the Outlook feature to use Word as mail editor:
- Restart the machine.
- Open Outlook
- Click Tools, click Options, and then click the Mail Format tab.
- Clear the Use Microsoft Word to edit e-mail messages check box**.**
- Clear the Use Microsoft Word to read Rich Text e-mail messages box.
- Exit Outlook.
- Restart the machine.
For more information on turning Word on or off as your e-mail editor see Turning Word on or off as your e-mail editor.
Impact of Workaround: Users will not be able to use Word as their e-mail editor or use Rich Text to read their e-mail
Using Group Policy
Domain administrators can use Group Policy to disable Word as the users e-mail editor. You do not have to restart the computer to implement this mitigation.
For information on using registry keys with a Group Policy see Using Administrative Template Files with Registry-Based Group Policy and Distributing Registry Changes.
Disable WordMail in Word 2003
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Options\Mail]
"EditorPreference"=dword:00020000
"UseWordMail"=dword:00000000
Disable WordMail in Word 2002
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Options\Mail]
"EditorPreference"=dword:00020000
"UseWordMail"=dword:00000000
Impact of Workaround: Users will not be able to use Word as their e-mail editor or use Rich Text by default to read their e-mail.
Step 2 Append /safe to the WINWORD.EXE Command Line
For Enterprise Customers
Using Word in Safe Mode helps protect the affected system from attempts to exploit this vulnerability.
All versions of Word have an application recovery feature that allows running Word in Safe mode. Safe mode disables the functionality and prevents vulnerable code from being exploited. The full set of limitations can be found at: https://office.microsoft.com/assistance/HP030823931033.aspx.
- Word will display SAFE MODE in the title bar if it is operating in Safe Mode.
- Right-click your desktop.
- Select New/Shortcut.
- Select Browse.
- Locate winword.exe**.**
- Append “ /safe” (without quotes) to the end of the file location, after the quotation mark.
- Click Next, and name your shortcut as “Word Safe Mode”.
- Click Finish.
To open a Word document, follow the steps listed below:
- Save your Word document to a disk or to your desktop.
- Start Word using your “Word Safe Mode” shortcut.
- Click File, click Open, and then browse to the document you want to open.
Impact of Workaround: Users that work in Safe mode will be subject to the limitations outlined in About Office Safe Mode.
Enterprise Customers Using Group Policy
Domain administrators can use Group Policy to enable Safe Mode for. You do not have to restart the computer to implement this mitigation.
Note Even after applying the workarounds that implements a registry change, do not open Word files directly from e-mail clients other than Outlook, for example MSN Hotmail, by double-clicking them
For information on using registry keys with a Group Policy see Using Administrative Template Files with Registry-Based Group Policy and Distributing Registry Changes.
Note Exact locations of registry keys depend on installation paths for Office used in each corporation. Registry keys will have to be determined by IT administrators to match their unique installation paths. The locations listed in the examples above correspond to the default installation paths for Microsoft Office. For example the default path for Office 10 on English Windows would be "c:\program files\microsoft office\office10".
Note To ensure Word is being loaded in Safe Mode when opening, editing or printing documents, the ‘Default’ and ‘Command’ registry values in the following registry keys should be edited to include the “/safe” command line parameter (without the quotes).
For example, if Office 2003 is installed the ‘Default’ value should be changed to look like this: "C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE" /n /dde /safe, and the ‘Command’ value should be changed to look like this: “']gAVn-}f(ZXfeAR6.jiWORDFiles>P`os,1@SW=P7v6GPl]Xh /n /dde /safe”.
Note The ‘Command’ value is an encoded string that is version-specific and language-specific, and it may not appear exactly as shown above on all systems.
[HKEY_CLASSES_ROOT\Word.Document.8\shell\Edit\command]
[HKEY_CLASSES_ROOT\Word.Document.8\shell\New\command]
[HKEY_CLASSES_ROOT\Word.Document.8\shell\Open\command]
[HKEY_CLASSES_ROOT\Word.Document.8\shell\OpenAsReadOnly\command]
[HKEY_CLASSES_ROOT\Word.Document.8\shell\Print\command]
[HKEY_CLASSES_ROOT\Word.Document.8\shell\Printto\command]
[HKEY_CLASSES_ROOT\Word.Backup.8\shell\New\command]
[HKEY_CLASSES_ROOT\Word.Backup.8\shell\Open\command]
[HKEY_CLASSES_ROOT\Word.Backup.8\shell\Print\command]
[HKEY_CLASSES_ROOT\Word.Backup.8\shell\Printto\command]
[HKEY_CLASSES_ROOT\Word.RTF.8\shell\Edit\command]
[HKEY_CLASSES_ROOT\Word.RTF.8\shell\New\command]
[HKEY_CLASSES_ROOT\Word.RTF.8\shell\Open\command]
[HKEY_CLASSES_ROOT\Word.RTF.8\shell\Print\command]
[HKEY_CLASSES_ROOT\Word.RTF.8\shell\Printto\command]
[HKEY_CLASSES_ROOT\Word.Template.8\shell\New\command]
[HKEY_CLASSES_ROOT\Word.Template.8\shell\Open\command]
[HKEY_CLASSES_ROOT\Word.Template.8\shell\Print\command]
[HKEY_CLASSES_ROOT\Word.Template.8\shell\Printto\command]
[HKEY_CLASSES_ROOT\Word.Wizard.8\shell\New\command]
Impact of Workaround: Users that work in Safe mode will be subject to the limitations outlined in this online help page: https://office.microsoft.com/assistance/HP030823931033.aspx
FAQ for Microsoft Word Code Malformed Object Pointer Vulnerability - CVE-2006-2492:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.
If a user is logged on with administrative user rights, 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. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
What causes the vulnerability?
When a user opens a specially crafted Word document using a malformed object pointer, it may corrupt system memory in such a way that an attacker could execute arbitrary code.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious 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.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user as an attachment and persuading the user to open the attachment.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.
Could I automatically be exploited when visiting a Web site using Word 2000?
While this vulnerability could not be exploited automatically when visiting a Web site using Word 2000, Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
What does the update do?
The update removes the vulnerability by modifying the way that Word validates the length of a message before it to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. While the initial report was provided through responsible disclosure, the vulnerability was later disclosed publicly. This security bulletin addresses the publicly disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.
Security Update Information
Word 2000
Prerequisites and Additional Update Details
Important Before you install this update, make sure that the following requirements have been met:
- Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
- Office 2000 Service Pack 3 (SP3) must be installed. Before you install this update, install Office 2000 SP3. For more information about how to install Office 2000 SP3, see Microsoft Knowledge Base Article 326585.
For more information about how to determine the version of Office 2000 that is installed on your computer, see Microsoft Knowledge Base Article 255275.
Inclusion in Future Service Packs
None. Service Pack 3 is the last service pack for Office 2000.
Restart Requirement
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Removal Information
After you install the update, you cannot remove it. To revert to an installation before the update was installed you must remove the application, and then install it again from the original CD-ROM.
Automated Client Installation Information
Office Update Web Site
We recommend that you install the Microsoft Office 2000 client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.
To have the Office Update Web site detect the updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Agree and Install to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update, review the following section.
Installation Information
The security update supports the following setup switches.
| Switch | Description |
|---|---|
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
| /q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a. |
| /r:a | Always restarts the computer after installation. |
| /r:s | Restarts the computer after installation without prompting the user. |
| /n:v | No version checking - Install the program over any earlier version. |
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Note The full file office update is intended for both client and administrative deployment scenarios.
Client Deployment Information
- Download this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this 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.
Word 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 9.0.0.8943 | 16-May-2006 | 05:08 | 8,831,028 |
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.
| Switch | Description |
|---|---|
| /? | Displays the command-line options. |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, follow these steps:
- Download this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file:
[path\name of EXE file] /c /t:C:\AdminUpdate
Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file. - Click Yes to accept the License Agreement.
- Click Yes if you are prompted to create the folder.
- If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK:
msiexec /a Admin Path**\**MSI File **/p C:\adminUpdate\**MSP File SHORTFILENAMES=TRUE
Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2000), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear. - Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
- Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:
msiexec /I Admin Path**\**MSI File **/qb REINSTALL=**Feature List REINSTALLMODE=vomu
Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2000), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.
To install all features, you can use REINSTALL=ALL or you can install the following features.
| Product | Feature |
|---|---|
| Word 2000 | WORDFiles |
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.
Administrative Installation File Information
The English version of this 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.
Word 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 9.0.0.8943 | 16-May-2006 | 05:08 | 8,831,028 |
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Word 2002
Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
- Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites:
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
- Office XP Service Pack 3 (SP3) must be installed. Before you install this update, install Office XP SP3. Additionally, if you are installing Office XP Multilingual User Interface Packs, you must install Multilingual User Interface Packs Service Pack 3 (SP3). For more information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671.
For more information about how to determine the version of Office XP that is installed on your computer, see Microsoft Knowledge Base Article 291331. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294.
Inclusion in Future Service Packs
None. Service Pack 3 is the last service pack for Office XP.
Restart Requirement
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Automated Client Installation Information
Microsoft Update Web Site
This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.
To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update, review the following section.
Installation Information
The security update supports the following setup switches.
| Switch | Description |
|---|---|
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
| /q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a. |
| /r:a | Always restarts the computer after installation. |
| /r:s | Restarts the computer after installation without prompting the user. |
| /n:v | No version checking - Install the program over any earlier version. |
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Note The full file office update is intended for both client and administrative deployment scenarios.
Client Deployment Information
- Download this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you see the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this 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.
Word 2002:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 10.0.6802.0 | 12-May-2006 | 02:39 | 10,709,776 |
Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.
| Switch | Description |
|---|---|
| /? | Displays the command-line options. |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file. |
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, follow these steps:
- Download this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file:
[path\name of EXE file] /c /t:C:\AdminUpdate
Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file. - Click Yes to accept the License Agreement.
- Click Yes if you are prompted to create the folder.
- If you are familiar with the procedure for updatingyouradministrative installation, click Start, click Run, type the following command, and then click OK:
msiexec /a Admin Path**\**MSI File **/p C:\adminUpdate\**MSP File SHORTFILENAMES=TRUE
Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeXp), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear. - Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
- Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstation configurations that were originally installed from this administrative installation. To do this, see the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:
msiexec /I Admin Path**\**MSI File **/qb REINSTALL=**Feature List REINSTALLMODE=vomu
Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeXP), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.
To install all features, you can use REINSTALL=ALL or you can install the following features.
| Product | Feature |
|---|---|
| Word 2002 | WORDFiles |
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On the home page of that site, look under the Update Strategies section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by the Windows Installer.
Administrative Installation File Information
The English version of this 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.
Word 2002:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 10.0.6802.0 | 12-May-2006 | 02:39 | 10,709,776 |
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. 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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Word 2003
Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
- To update Word 2003, Word 2003 Service Pack 1 or Word 2003 Service Pack 2 must be installed. Before you install this update, install Office 2003 SP1 or Office 2003 SP2.
- To update Word Viewer 2003, the latest version of Word 2003 Viewer must be installed. Download the lasted Word 2003 Viewer.
For more information about how to determine the version of Office 2003 that is installed on your computer, see Microsoft Knowledge Base Article 821549. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294.
Inclusion in Future Service Packs:
The fix for this issue will be included in a future service pack.
Restart Requirement
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Removal Information
To remove this security update, use Add or Remove Programs in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from Add or Remove Programs in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Automated Client Installation Information
Microsoft Update Web Site
This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.
To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update, review the following section.
Installation Information
The security update supports the following setup switches.
| Switch | Description |
|---|---|
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
| /q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a. |
| /r:a | Always restarts the computer after installation. |
| /r:s | Restarts the computer after installation without prompting the user. |
| /n:v | No version checking - Install the program over any earlier version. |
Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Note The full file office update is intended for both client and administrative deployment scenarios.
Client Deployment Information
- Download the security update for Word 2003and/or download the security update for Word 2003 Viewer.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that states the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this 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.
Word 2003:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 11.0.8026.0 | 15-May-2006 | 21:39 | 12,148,496 |
Word 2003 Viewer:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Wordview.exe | 11.0.8026.0 | 15-May-2006 | 21:39 | 6,958,864 |
Administrative Installation Information
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.
| Switch | Description |
|---|---|
| /? | Displays the command-line options. |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file. |
For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, follow these steps:
- Download the security update for Word 2003and/or download the security update for Word 2003 Viewer.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file:
[path\name of EXE file] /c /t:C:\AdminUpdate
Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file. - Click Yes to accept the License Agreement.
- Click Yes if you are prompted to create the folder.
- If you are familiar with the procedure for updating your administrative installation**,** click Start, click Run, type the following command, and then click OK:
msiexec /a Admin Path**\**MSI File **/p C:\adminUpdate\**MSP File SHORTFILENAMES=TRUE
Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear. - Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
- Click I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions such as repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:
Msiexec /I Admin Path**\**MSI File **/qb REINSTALL=**Feature List REINSTALLMODE=vomu
Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.
To install all features, you can use REINSTALL=ALL or you can install the following features
| Product | Feature |
|---|---|
| Word 2003 | WORDFiles |
| Word 2003 Viewer | WORDVIEWFiles |
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On the home page of that site, look under the Update Strategies section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by the Windows Installer.
Administrative Installation File Information
The English version of this 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.
Word 2003:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Winword.exe | 11.0.8026.0 | 15-May-2006 | 21:39 | 12,148,496 |
Word 2003 Viewer:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Wordview.exe | 11.0.8026.0 | 15-May-2006 | 21:39 | 6,958,864 |
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. 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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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. - 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Shih-hao Weng of Information & Communication Security Technology Center for reporting the Microsoft Word Malformed Object Pointer Vulnerability - CVE-2006-2492.
- Andreas Marx of AV-Test.org for working with Microsoft on the Microsoft Word Malformed Object Pointer Vulnerability - CVE-2006-2492.
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available at the Microsoft Update Web site.
Support:
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- 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.
Security Resources:
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Windows Server Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Microsoft Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.
Windows Server Update Services:
By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.
For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
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 (June 13, 2006): Bulletin published.
- V1.1 (June 14, 2006): Bulletin revised: Bulletin revised: Updated the” Acknowledgments” section for CVE-2006-2492.
- V1.2 (June 21, 2006): Bulletin revised: Updated the “What updates does this release replace?” regarding MS06-012 for Word 2003.
- V1.3 (July 12, 2006): Bulletin updated the “What updates does this release replace?” regarding MS05-023 for Word 2003.
Built at 2014-04-18T13:49:36Z-07:00