Export (0) Print
Expand All

Microsoft Security Bulletin MS07-001 - Important

Vulnerability in Microsoft Office 2003 Brazilian Portuguese Grammar Checker Could Allow Remote Code Execution (921585)

Published: January 09, 2007

Version: 1.0

Summary

Who Should Read this Document: Customers who use Microsoft Office 2003 Brazilian Portuguese Grammar Checker

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:

  • Microsoft Office 2003 Service Pack 2 (Brazilian Portuguese Version)- Download the update (KB921585)
    • Microsoft Word 2003
    • Microsoft Excel 2003
    • Microsoft Outlook 2003
    • Microsoft Access 2003
    • Microsoft OneNote 2003
    • Microsoft PowerPoint 2003
    • Microsoft Publisher 2003
    • Microsoft Access 2003
    • Microsoft InfoPath 2003
    • Microsoft FrontPage 2003
    • Microsoft Visio 2003
    • Microsoft Visio Enterprise Architects 2003
  • Microsoft Office Multilingual User Interface 2003 Service Pack 2 - Download the update (KB921585)
  • Microsoft Project Multilingual User Interface 2003 Service Pack 2 - Download the update (KB921585)
  • Microsoft Visio Multilingual User Interface 2003 Service Pack 2 - Download the update (KB921585)
  • Microsoft Office Proofing Tools 2003 Service Pack 2 - Download the update (KB921585)

Non-Affected Software:

  • Microsoft Office 2000
  • Microsoft Office XP
  • Microsoft Office 2007
  • Microsoft Office v.X for Mac
  • Microsoft Office 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.

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:

This update resolves a newly discovered, publicly reported vulnerability. The vulnerability is documented in its own subsection in the "Vulnerability Details" section of this bulletin.

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.

We recommend that customers should apply the update at the earliest opportunity.

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft Office 2003 (Brazilian Portuguese Version) and Microsoft Office Proofing Tools 2003Microsoft Office Multilingual User Interface 2003Microsoft Project Multilingual User Interface 2003 and Microsoft Visio Multilingual User Interface 2003
Office 2003 Brazilian Portuguese Grammar Checker Vulnerability - CVE-2006-5574Remote Code ExecutionImportantImportantImportant

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.

Do all Office 2003 users need to install the Microsoft Office 2003 Brazilian Portuguese Grammar Checker security update?
No, you will only need to install this update if you have a Brazilian Portuguese or Spanish language version of one of the products listed in the “Affected Products” section.

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.

SoftwareMBSA 1.2.1MBSA 2.0
Microsoft Office 2003YesYes
Microsoft Office Multilingual User Interface 2003YesYes
Microsoft Project Multilingual User Interface 2003YesYes
Microsoft Visio Multilingual User Interface 2003YesYes
Microsoft Office Proofing Tools 2003YesYes

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

ProductSMS 2.0SMS 2003
Microsoft Office 2003 YesYes
Microsoft Office Multilingual User Interface 2003YesYes
Microsoft Project Multilingual User Interface 2003YesYes
Microsoft Visio Multilingual User Interface 2003YesYes
Microsoft Office Proofing Tools 2003YesYes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, 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 (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, 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.

For more detailed information, see Microsoft Knowledge Base Article 910723.

Office 2003 Brazilian Portuguese Grammar Checker Vulnerability - CVE-2006-5574:

A remote code execution vulnerability exists in Office 2003 Brazilian Portuguese Grammar Checker. An attacker could exploit this vulnerability when Office opens a file and parses the text.

If a user were 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 Office 2003 Brazilian Portuguese Grammar Checker Vulnerability - CVE-2006-5574:

  • 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.
  • In a Web-based attack scenario, an attacker would have to host a Web site that contains Office files that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a 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.
  • 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 or reply to an e-mail if Word is being used as the e-mail editor.

Workarounds for Office 2003 Brazilian Portuguese Grammar Checker Vulnerability - CVE-2006-5574:

  • Do not open or save Microsoft Office 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.

FAQ for Office 2003 Brazilian Portuguese Grammar Checker Vulnerability - CVE-2006-5574:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office 2003 Brazilian Portuguese Grammar Checker. An attacker could exploit this vulnerability when Office opens a file and parses the text.

If a user were 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?
The Office 2003 Brazilian Portuguese Grammar Checker does not perform sufficient data validation when Office opens a file and parses the text. 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 an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file or reply to an e-mail if Word is being used as the e-mail editor.

In a Web-based attack scenario, an attacker would have to host a Web site that contains Office files that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability An attacker would have no way to force users to visit a 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.

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 Office 2003 Brazilian Portuguese Grammar Checker parses the text before passing it to the allocated buffer.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Affected Software:

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

Office 2003

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirements have been met:

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
SwitchDescription
/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 the security update for Office 2003 and/or Microsoft Office Multilingual User Interface 2003 and/or Microsoft Project Multilingual User Interface 2003 and/or Visio Multilingual User Interface 2003 and/or Microsoft Office Proofing Tools 2003.
  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 NameVersionDateTimeSize
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA17-Aug-200616:101,863,468

Microsoft Office Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA17-Aug-200616:101,863,468
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Microsoft Project Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA17-Aug-200616:101,863,468
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Visio Multilingual User Interface 2003:

File NameVersionDateTimeSize
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA17-Aug-200616:101,863,468

Microsoft Office Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA17-Aug-200616:101,863,468
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Office Proofing Tools 2003 Service Pack 2:

File NameVersionDateTimeSize
Imekr70.ime7.0.8002.010-Nov-200520:14103,624
Juridsch.dicNA30-Sep-200519:1793,727
Maatsch.dicNA30-Sep-200519:37162,288
Medisch.dicNA30-Sep-200519:17238,139
Msgr3en.dll3.1.0.912628-Jul-200604:391,407,800
Msgren32.dll7.0.1.321-Aug-200617:12529,984
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA26-Sep-200521:284,890,875
Msgr_en.lexNA17-Aug-200616:101,863,468
Mso.aclNA18-Oct-200500:229,624
Mssp3en.lexNA20-Jul-200617:492,528,721
Mssp3en.lexNA08-Mar-200618:35925,482
Mssp3gep.lexNA20-Jul-200618:492,614,059
Msspell3.dll2.54.0.020-Jul-200620:05353,816
Msspell3.dll3.0.7.908-Mar-200618:35194,112
Msth3am.lexNA14-Sep-200519:40753,046
Techwet.dicNA30-Sep-200519:17168,270
Zakelijk.dicNA30-Sep-200519:17259,080

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
SwitchDescription
/? 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 the security update for Office 2003 and/or Microsoft Office Multilingual User Interface 2003 and/or Microsoft Project Multilingual User Interface 2003 and/or Visio Multilingual User Interface 2003 and/or Microsoft Office Proofing Tools 2003.
  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:

    [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.
  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:

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

ProductFeature
VISVEA, ACC11, BASIC11, FP11, ONOTE11, OUTLS11, OUTL11, PPT11, PROI11, PRO11, PUB11, STDP11, STD11, WORD11, INF11, EXCEL11, PRJPROE, PRJPRO, PRJSTDE, PRJSTD, VISPRO, VISPROR, VISSTD, VISSTDRSpellingAndGrammarFiles_1046

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 2003:

File NameVersionDateTimeSize
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408

Microsoft Office Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Microsoft Project Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Visio Multilingual User Interface 2003:

File NameVersionDateTimeSize
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408

Microsoft Office Multilingual User Interface 2003:

File NameVersionDateTimeSize
Contab32.dll11.0.8008.010-Jan-200600:44116,424
Dumpster.dll11.0.8036.015-Jul-200601:3732,016
Emablt32.dll11.0.8020.004-Apr-200601:22106,696
Emsabp32.dll11.0.8109.023-Sep-200607:12264,976
Emsmdb32.dll11.0.8109.023-Sep-200607:12706,320
Emsui32.dll11.0.8032.022-Jun-200602:43132,368
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msmapi32.dll11.0.8115.003-Nov-200601:491,414,928
Mspst32.dll11.0.8023.020-Apr-200621:42725,776
Msspell3.dll7.0.12.1310-Aug-200518:07434,176
Outex.dll11.0.8113.019-Oct-200601:37654,608
Pstprx32.dll11.0.8000.022-Oct-200523:15280,264
Scanpst.exe11.0.6802.004-Oct-200517:3460,136
Xlintl32.dll11.0.6802.004-Oct-200514:16814,312

Office Proofing Tools 2003 Service Pack 2:

File NameVersionDateTimeSize
Imekr70.ime7.0.8002.010-Nov-200520:14103,624
Medisch.dicNA 30-Sep-200519:17238,139
Msgr3en.dll3.1.0.912628-Jul-200604:391,407,800
Msgren32.dll7.0.1.321-Aug-200617:12529,984
Msgren32.dll12.0.0.1606-Oct-200618:261,292,408
Msgr_en.lexNA 26-Sep-200521:284,890,875
Msgr_en.lexNA 17-Aug-200616:101,863,468
Mso.aclNA 18-Oct-200500:229,624
Mssp3en.lexNA 20-Jul-200617:492,528,721
Mssp3en.lexNA 08-Mar-200618:35925,482
Mssp3gep.lexNA 20-Jul-200618:492,614,059
Msspell3.dll2.54.0.020-Jul-200620:05353,816
Msspell3.dll3.0.7.908-Mar-200618:35194,112
Msth3am.lexNA 14-Sep-200519:40753,046
Techwet.dicNA 30-Sep-200519:17168,270
Zakelijk.dicNA 30-Sep-200519:17259,080

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

Note 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 Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

    Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Other Information

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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:

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 Scan 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 (January 9, 2007): Bulletin published.

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft