Microsoft Security Bulletin MS07-013
Vulnerability in Microsoft RichEdit Could Allow Remote Code Execution (918118)
Version: 1.2
Summary
Who Should Read this Document: Customers who use Microsoft Windows and/or Microsoft Office
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Important
Recommendation: Customers should apply the update at the earliest opportunity
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
Windows Software:
| • | Microsoft Windows 2000 Service Pack 4 — Download the update |
| • | 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 |
Office Software:
| • | Microsoft Office 2000 Service Pack 3 — Download the update (KB920906)
| ||||||||||||||||||||||||
| • | Microsoft Office XP Service Pack 3 — Download the update (KB920816)
| ||||||||||||||||||||||||
| • | Microsoft Office 2003 Service Pack 2 — Download the update (KB920813)
| ||||||||||||||||||||||||
| • | Microsoft Project 2000 Service Release 1 - Download the update (KB920906) | ||||||||||||||||||||||||
| • | Microsoft Office 2000 Multilanguage Packs — Download the update (KB920906) | ||||||||||||||||||||||||
| • | Microsoft Project 2002 Service Pack 1 - Download the update (KB920816) | ||||||||||||||||||||||||
| • | Microsoft Visio 2002 Service Pack 2 - Download the update (KB920816) | ||||||||||||||||||||||||
| • | Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office - Download the update (KB929437) | ||||||||||||||||||||||||
| • | Microsoft Global Input Method Editor for Office 2000 (Japanese) - Download the update (KB920906) | ||||||||||||||||||||||||
| • | Microsoft Office 2004 for Mac - Download the update (KB932185) |
Non-Affected Software:
| • | Windows Vista |
| • | 2007 Microsoft Office System |
| • | Microsoft Office 2003 Service Pack 2
|
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 addresses a newly discovered, privately reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
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 impacted than users who operate with administrative user rights.
We recommend that customers apply the update at the earliest opportunity.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Microsoft Office 2000, Microsoft Office XP, and Microsoft Office 2003 | Learning Essentials 1.0, 1.1, 1.5 for Microsoft Office, and Microsoft Global Input Method Editor for Office 2000 (Japanese) | Microsoft Office 2004 for Mac | Microsoft Windows 2000 Service Pack 4 | Microsoft Windows XP Service Pack 2 | Microsoft Windows Server 2003 (All Versions) |
Microsoft RichEdit Vulnerability - CVE-2006-1311 | Remote Code Execution | Important | Important | Important | Important | Important | Important |
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 The severity ratings for Project 2002, Visio 2002, Project 2000, Office 2000 Multilanguage packs, and Global Input Method Editor for Office map to the Office 2000, Office XP and Office 2003 applications.
Note The security updates for 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 Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating. |
| • | The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating. |
| • | The Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating. |
| • | The Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 severity rating. |
Frequently Asked Questions (FAQ) Related to This Security Update |
Does this security update remove the same vulnerability as those addressed in MS07-011 and MS07-012?
No, each individual security bulletin addresses unique security vulnerabilities in different software components; however, similarities do exist between the three security bulletins in how an attacker could exploit the vulnerabilities. It should be noted that MS07-011 (OLE) includes a defense-in-depth improvement that help block known attack vectors to the vulnerability addressed in MS07-012 (MFC). Even with the MS07-011 defense-in-depth improvement, Microsoft strongly that all three security updates be deployed to address all known vulnerabilities.
Do I need to deploy this security update before MS07-011 and MS07-012?
No, the security updates in the three security bulletins can be deployed in any order. There are no application compatibility dependencies between the security updates in the three security bulletins.
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 Office 2000 Service Pack 3 | Yes (ODT) | No |
Microsoft Office XP Service Pack 3 | Yes (ODT) | Yes |
Microsoft Office 2003 Service Pack 2 | Yes (ODT) | Yes |
Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office | Yes (ODT) | Yes |
Microsoft Office 2004 for Mac | No | No |
Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
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 |
Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.
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 detailed information, see Microsoft Knowledge Base Article 910723.
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 Office 2000 Service Pack 3 | Yes | Yes |
Microsoft Office XP Service Pack 3 | Yes | Yes |
Microsoft Office 2003 Service Pack 2 | Yes | Yes |
Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office | Yes | Yes |
Microsoft Office 2004 for Mac | No | No |
Microsoft Windows 2000 Service Pack 4 | Yes | Yes |
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 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.
Note If you have used an Administrative Installation Point for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline.
| • | For more information about how to change the source for a client computer from an updated administrative installation point to an Office 2000 original baseline source or Service Pack 3 (SP3) see, Microsoft Knowledge Base Article 932889. |
| • | For more information on how to change the source for a client computer from an updated administrative installation point to an Office XP original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 922665. |
| • | For more information about how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 2 (SP2) see, Microsoft Knowledge Base Article 902349. |
For more information about SMS, visit the SMS Web site.
Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1 has reached the end of its support life cycle. 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.
Extended security update support for Microsoft 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, and Windows Millennium Edition have 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.
Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems; what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have 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.
Customers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Details |
Microsoft RichEdit Vulnerability - CVE-2006-1311: |
A remote code execution vulnerability exists in the RichEdit components provided with Microsoft Windows and Microsoft Office. An attacker could attempt to exploit this vulnerability when a user interacts with a malformed embedded OLE object within a Rich Text Format (RTF) file or a Rich Text e-mail message.
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 RichEdit Vulnerability - CVE-2006-1311: |
| • | 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. |
| • | An attacker could only exploit this vulnerability when a user opens and then interacts with an embedded OLE object within a Rich Text Format (RTF) file or a Rich Text e-mail message. |
| • | 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 RTF 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, and then convince the user to open the file in a Microsoft Office application. |
| • | The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message and then interact with an embedded OLE object within a Rich Text Format (RTF) file, or interact with an embedded OLE object within a Rich Text e-mail message. |
Workarounds for Microsoft RichEdit Vulnerability - CVE-2006-1311: |
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.
| • | Enable Embedded Object blocking in WordPad Note: This workaround only applies to Microsoft Windows XP Service Pack 2, Microsoft Windows Server 2003, and Microsoft Windows Server 2003 Service Pack 1 systems. Wordpad.exe is the default application used to open Rich Text files. Users can temporarily block the parsing of embedded objects within Rich Text Files. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. We recommend that you back up the registry before you edit it. Use the following text to create a .reg file that will automate editing of the registry to temporarily block the parsing of embedded objects with Rich Text Files when using Wordpad.exe. You can copy the following text, paste it into a text editor such as Notepad, and then save the file with the .reg file name extension. Run the .reg file on the vulnerable client. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RtfStreamIn\ObjectBlocking\wordpad.exe] Impact of Workaround: Wordpad.exe will no longer parse embedded objects within Rich Text files. | ||||||
| • | Do not open or save RTF files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file. | ||||||
| • | Un-install WordPad from Windows 2000 or Windows 2003 Wordpad.exe is the default application used to open Rich Text files. By uninstalling WordPad, users can block the parsing of embedded objects within Rich Text Files.
Impact of Workaround: Wordpad will no longer parse embedded objects within Rich Text files. |
FAQ for Microsoft RichEdit Vulnerability - CVE-2006-1311: |
What is the scope of the vulnerability?
A remote code execution vulnerability exists in the RichEdit components provided with Microsoft Windows and Microsoft Office. An attacker could exploit this vulnerability when a user interacts with a malformed embedded OLE object within a Rich Text Format (RTF) file, or a Rich Text e-mail message.
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 is Rich Text Format (RTF)?
The Rich Text Format (RTF) Specification provides a format for text and graphics interchange that can be used with different output devices, operating environments, and operating systems.
What is OLE?
By using OLE technology, an application can provide embedding and linking support. OLE is the technology that applications use to create and edit compound documents. These are documents of one format, such as a Microsoft Word document, that contain embeddings of (or links to) documents of another format, such as Microsoft Excel. OLE 2.0 takes OLE even further by allowing in-place editing. Instead of launching a new application when an OLE object is activated, the user instead sees a new set of menu items inside their existing application. For more information about OLE, visit the following Microsoft Web site.
What causes the vulnerability?
Microsoft Windows and Office RichEdit components do not perform sufficient validation when parsing OLE objects embedded within RTF files. When a user interacts with a malformed embedded OLE Object within an RTF file, 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 cause arbitrary code to run with the privileges of the user who opened the file.
How could an attacker exploit the vulnerability?
An attacker could only exploit this vulnerability when a user opens and then interacts with an embedded OLE object within a Rich Text Format (RTF) file or a Rich Text e-mail message.
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 RTF 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, and then convince the user to open the file in a Microsoft Office application.
The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message and then interact with an embedded OLE object within the RTF file, or interact with an embedded OLE object within a Rich Text e-mail message.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
The update removes the vulnerability by modifying the way that the Microsoft Windows and Office RichEdit components parse OLE streams within RTF.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Security Update Information |
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Office 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. |
| • | To install the Project 2000 Service Release 1 (SR1) update, Project 2000 Service Release 1 (SR1) must be installed. Before you install this update, install Project 2000 SR1. For more information about how to install Project 2000 SR1, see Microsoft Knowledge Base Article 288953. |
| • | To install the MultiLanguage Pack update, Office 2000 Service Pack 3 (SP-3) for MultiLanguage Pack must be installed. Before you install this update, install Service Pack 3 (SP-3) for Multilanguage Pack. For more information about how to install Service Pack 3 (SP-3) for Multilanguage Pack, see Office 2000 Service Pack 3 (SP-3) for MultiLanguage Pack. |
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 which installation you have 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.
| Supported Security Update Installation 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 | Overrides the install command that is 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
1. | Download this security update for Office 2000 and/or Project 2000 Service Pack 1 and/or Office 2000 Multilanguage Packs SP3. |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file. |
5. | If you are prompted to install the update, click Yes. |
6. | Click Yes to accept the License Agreement. |
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK. |
8. | 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.
Office 2000:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
Office 2000 Multilanguage Packs:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
Project 2000 Service Pack 1:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
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.
| Supported Security Update Installation Switches | |
| 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:
1. | Download this security update for Office 2000 and/or Project 2000 Service Pack 1 and/or Office 2000 Multilanguage Packs SP3. |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | 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: |
5. | Click Yes to accept the License Agreement. |
6. | Click Yes if you are prompted to create the folder. |
7. | If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: |
8. | Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. |
9. | 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.
Office 2000:
| Product | Feature |
O9ACC, O9PRM, O9PRO | ProductNonBootFiles, ACCESSNonBootFiles |
MSPUB, O9PUB, O9PB, O9PRMCD2 | CD2NonBootFiles, PubNonBootFiles |
O9ART | AccessRuntimeMaster |
O9EXL, O9OLK, O9SBE, O9FP, O9PP, O9STD, O9WRD, 9327_o9procd1_sbe_coxs_slv_data1 | ProductNonBootFiles |
O9PIPC1, O9PIPC2, O9WDI, 9327_o9sr1std_crxs_JPN_DATA1 | AsiaIMESetupFiles, ProductNonBootFiles |
9327_o9sr1PRMcd1_crxs_JPN_DATA1, 9327_o9sr1procd1_crxs_JPN_DATA1 | AsiaIMESetupFiles, ProductNonBootFiles, ACCESSNonBootFiles |
Office 2000 Multilanguage Pack:
| Product | Feature |
O9LPKCD2 | AsiaIMESetupFiles_JPN, RichEdit |
Project 2000:
| Product | Feature |
Project 2000 | ProductNonBootFiles |
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.
Office 2000:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
Office 2000 Multilanguage Packs:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
Project 2000 Service Pack 1:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.30.23.1227 | 16-Nov-2006 | 17:05 | 433,152 |
Verifying that the Update Has Been Applied
| • | Microsoft Baseline Security Analyzer |
Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.
| • | File Version Verification |
Note Because there are several versions of Microsoft Office, 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. |
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. |
Office XP |
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. For more information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671. |
| • | To install the Project 2002 Service Pack 1 (SP1) update, Project 2002 Service Pack 1 (SP1) must be installed. Before you install this update, install Project 2000 SR1. For more information about how to install see Project 2002 Service Pack 1 (SP1). |
| • | To install the Visio 2002 Service Pack 2 (SP2) update, Visio 2002 Service Pack 2 (SP2) must be installed. Before you install this update, install Service Pack 3 (SP-3) for Multilanguage Pack. For more information about how to install Visio 2002 Service Pack 2 (SP2), Visio 2002 Service Pack 2 (SP2). |
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.
Note For Project 2002 Service Pack 1 and Visio 2002 Service Pack 2, 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 |
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.
| Supported Security Update Installation 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 | Overrides the install command that is 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
1. | Download this security update for Office XP and/or Project 2002 Service Pack 1 and/or Visio 2002 Service Pack 2. |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file. |
5. | If you are prompted to install the update, click Yes. |
6. | Click Yes to accept the License Agreement. |
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK. |
8. | 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.
Office XP:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
Project 2002 Service Pack 1:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
Visio 2002 Service Pack 2:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
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.
| Supported Security Update Installation Switches | |
| 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:
1. | Download this security update for Office XP and/or Project 2002 Service Pack 1 and/or Visio 2002 Service Pack 2. |
2. | 2.Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | 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: |
5. | Click Yes to accept the License Agreement. |
6. | Click Yes if you are prompted to create the folder. |
7. | If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: |
8. | Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. |
9. | 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 |
ACCESS, FP, OUTLOOK, PIPC1, PPT, PROPLUS, ACCESSRT, PRO, PUB, SBE, STD, STDEDU, WORD, EXCEL | ProductFiles |
Project 2002 | ProductFiles |
Visio 2002 | Product_Files |
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.
Office XP:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
Project 2002 Service Pack 1:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
Visio 2002 Service Pack 2:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.40.11.2220 | 24-Aug-2006 | 21:09 | 650,056 |
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 commonly misconfigured security parameters. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
| • | File Version Verification |
Note Because there are several versions of Microsoft Office, 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. |
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. |
Office 2003 |
Prerequisites and Additional Update Details |
Important: Before you install this update, make sure that the following requirements have been met:
| • | To update Office 2003, Office 2003 Service Pack 2 must be installed. Before you install this update, install Office 2003 SP2. |
| • | To install the update for Project 2003 Service Pack 2, Project 2003 Service Pack 2 must be installed. Before you install this update, install Project 2003 SP2. For additional information about how to install Project 2003 Service Pack 2, see Microsoft Knowledge Base Article 887620. |
| • | To install the update for Visio 2003 Service Pack 2, Visio 2003 Service Pack 2 must be installed. Before you install this update, install Visio 2003 SP2. For additional information about how to install Visio 2003 Service Pack 2, see Microsoft Knowledge Base Article 838345 . |
| • | To install the update for OneNote 2003 Service Pack 2, OneNote 2003 Service Pack 2 must be installed. Before you install this update, install OneNote SP2. For additional information about how to install OneNote Service Pack 2, see Microsoft Knowledge Base Article 887619. |
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.
| Supported Security Update Installation 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 | Overrides the install command that is 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
1. | |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file. |
5. | If you are prompted to install the update, click Yes. |
6. | Click Yes to accept the License Agreement. |
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK. |
8. | 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.
Office 2003:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.50.99.2014 | 17-Aug-2006 | 23:23 | 1,125,216 |
Project 2003:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.50.99.2014 | 17-Aug-2006 | 23:23 | 1,125,216 |
Visio 2003:
| File Name | Version | Date | Time | Size |
Riched20.dll | 5.50.99.2014 | 17-Aug-2006 | 23:23 | 1,125,216 |
OneNote 2003:
| File Name | Version | Date | Time |