[THIN] Alert: Vulnerability in TNEF Decoding in Microsoft Outlook and Microsoft Exchange Could Allow Remote Code Execution (902412)

  • From: "Jim Kenzig http://ThinHelp.com" <jkenzig@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx, windows2000@xxxxxxxxxxxxx
  • Date: Wed, 11 Jan 2006 10:31:01 -0800 (PST)

Heads Up! This one is critical.
JK
 
http://www.microsoft.com/technet/security/bulletin/MS06-003.mspx
 
Microsoft Security Bulletin MS06-003
Vulnerability in TNEF Decoding in Microsoft Outlook and Microsoft Exchange 
Could Allow Remote Code Execution (902412)
Published: January 10, 2006

Version: 1.0
Summary
Who should read this document: Customers who use Microsoft Outlook, Microsoft 
Exchange, or customers who have the Microsoft Office Multilingual User 
Interface (MUI) Packs, Microsoft Multilanguage Packs or Microsoft Office 2003 
Language Interface Packs (LIPS) installed.
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately.
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software: 
âMicrosoft Office 2000 Service Pack 3
Microsoft Office 2000 Software:
âMicrosoft Outlook 2000 â Download the update (KB892842)
âMicrosoft Office 2000 MultiLanguage Packs â Download the update (KB892842)
âMicrosoft Outlook 2000 English MultiLanguage Packs â Download the update 
(KB892842)

âMicrosoft Office XP Service Pack 3
Microsoft Office XP Software:
âMicrosoft Outlook 2002 â Download the update (KB892841)
âMicrosoft Office XP Multilingual User Interface Packs â Download the 
update (KB892841)

Note Multilingual User Interface Packs are for non- English packages.

âMicrosoft Office 2003 Service Pack 1 and Service Pack 2
Microsoft Office 2003 Software:
âMicrosoft Outlook 2003 â Download the update (KB892843)
âMicrosoft Office 2003 Multilingual User Interface Packs â Download the 
update (KB892843)
âMicrosoft Office 2003 Language Interface Packs â Download the update 
(KB887617)

Note Multilingual User Interface Packs are for non- English packages

âMicrosoft Exchange Server
âMicrosoft Exchange Server 5.0 Service Pack 2 â Download the update 
(KB894689)
âMicrosoft Exchange Server 5.5 Service Pack 4â Download the update 
(KB894689)
âMicrosoft Exchange 2000 Server Pack 3 with the Exchange 2000 Post-Service 
Pack 3 Update Rollup of August 2004 â Download the update (894689)


Non-Affected Software:
âMicrosoft Exchange Server 2003 Service Pack 1
âMicrosoft Exchange Server 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.
For more information about Exchange 2000 Server Post-Service Pack 3 Update 
Rollup see Microsoft Knowledge Base Article 870540.
Top of section
General Information
Executive Summary

Executive Summary:
This update resolves a newly-discovered, privately-reported vulnerability that 
could allow an attacker to run arbitrary code on the system. The vulnerability 
is documented in the âVulnerability Detailsâ section of this bulletin.
On vulnerable versions of Outlook, Office Language Interface Packs, Office 
MultiLanguage Packs or Office Multilingual User Interface Packs, 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.
On vulnerable versions of Exchange, an attacker who successfully exploited this 
vulnerability could take complete control of an affected system. This 
vulnerability could be exploited automatically without user interaction. An 
attacker could then install programs; view, change, or delete data; or create 
new accounts with full user rights.
We recommend that customers apply the update immediately.
Severity Ratings and Vulnerability Identifiers:
Vulnerability IdentifiersImpact of VulnerabilityOutlook 2000, Outlook 2002, 
Outlook 2003Office 2000 MultiLanguage Packs (MUI), Office XP Multilingual User 
Interface Packs (MUI), Office 2003 Multilingual User Interface Packs (MUI) or 
Office 2003 Language Interface Packs (LIP)Exchange Server 5.0, Exchange Server 
5.5, Exchange 2000 Server
TNEF Decoding Vulnerability - CVE-2006-0002Remote Code 
ExecutionCriticalCriticalCritical

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.
Top of section
Frequently asked questions (FAQ) related to this security update

What are Office 2000 MultiLanguage Packs (MUI)?
Office 2000 MultiLanguage Packs provide features that allow users to change the 
language of their Office user interface and online Help. It includes the 
Microsoft Office Proofing Tools, which provide spelling checkers, grammar 
checkers, and other tools for editing in a variety of languages.
What are Office XP and Office 2003 Multilingual User Interface Packs (MUI)?
Office 2003 Multilingual Packs and Office 2003 Editions with MUI Pack can help 
simplify worldwide Microsoft Office deployment for multinational organizations 
or for organizations that have multilingual employees. With the MUI Pack, 
organizations can deploy a single version of Office 2003 Editions and still 
meet the requirements of users who work in other languages. IT administrators 
simply provide the user interface (UI) and Help files for different languages 
based on each individual's needs.
What is Office 2003 Language Interface Pack (LIP)?
Office 2003 Language Interface Packs are designed for regional markets that 
currently do not have local versions, the Language Interface Pack (LIP) 
provides computer users with the ability to adapt their copy of Office to 
display many commonly used features in their native language. It includes the 
Microsoft Office Proofing Tools; the Proofing Tools provide spelling checkers, 
grammar checkers, and other tools for editing in a variety of languages.
Why are there separate updates for Outlook Exchange Server 2003 (MUI), Office 
2000 MultiLanguage Packs (MUI), Office XP Multilingual User Interface Packs 
(MUI) Office 2003 Multilingual User Interface Packs (MUI) or Office 2003 
Language Interface Pack (LIP)?
The reason that this issue is addressed separately in versions of Exchange 
Server and Office software is that Transport Neutral Encapsulation Format 
(TNEF) decoding components differ between server and client software. Customers 
must apply all relevant updates.
I do not have Outlook installed, but I have Office 2000 MultiLanguage Packs 
(MUI), Office 2003 Multilingual User Interface Packs(MUI), Office XP 
Multilingual User Interface Packs (MUI) or Office 2003 Language Interface Packs 
(LIP) installed. Do I need to apply the update?
Although the only identified attack vector is Outlook, we recommend that you 
install the security updates if you have any of the affected software installed.
I am using Outlook and I have Office 2000 MultiLanguage Packs (MUI), Office XP 
Multilingual User Interface Packs (MUI),Office 2003 Multilingual User Interface 
Packs (MUI) installed or Office 2003 Language Interface Packs (LIP). Am I 
vulnerable?
Yes. You should install the Outlook security update and relevant security 
updates for the Office 2000 MultiLanguage Packs, the Office XP Multilingual 
User Interface Packs the Office 2003 Multilingual User Interface Packs, and the 
Office 2003 Language Interface Pack.
I am still using Microsoft Exchange 5.0 Server or Microsoft Exchange 5.5 
Server. Originally, extended security update support ended on December 31, 
2005. This bulletin has a security update for Microsoft Exchange 5.0 Server or 
Microsoft Exchange 5.5 Server. Why is that?
Microsoft Exchange 5.0 Server or Microsoft Exchange 5.5 Server had reached the 
end of their life cycles on December 31, 2005. However, in order to create 
greater consistency and predictability for customers, Microsoft is matching the 
date that the product support lifecycle ends, with the regular monthly security 
update release cycle.

Exchange 5.0 Server or Exchange 5.5 Server extended security support ends on 
January 10, 2006.

For more information about the Windows Service Pack Product Life Cycle, visit 
the Microsoft Support Lifecycle Web site. For more information about the 
Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine 
whether this update is required?
MBSA 1.2.1 will determine whether this update is required for Exchange 5.0, 
Exchange 5.5 Server and Exchange 2000 Server. For more information about MBSA, 
visit the MBSA Web site.

MBSA 1.2.1 for Microsoft Office will determine and support local scans for 
Office 2000, Office XP, Office 2003, Office XP Multilingual User Interface 
Packs, and Office 2003 Multilingual User Interface Packs. MBSA uses an 
integrated version of the Office Detection Tool (ODT) which does not support 
remote scans of this issue. For more information about MBSA, visit the MBSA Web 
site. For more information about MBSA support, visit the following Microsoft 
Baseline Security Analyzer 1.2 Q&A Web site.

Note Microsoft Baseline Security Analyzer (MBSA) 1.2.1 will not determine 
whether this update is required for Microsoft Office 2003 Language Interface 
Packs.
Note the Office Detection Tool (ODT) will not determine whether this update is 
required for Microsoft Office 2003 Language Interface Packs.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine 
whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required for Office XP, 
Office 2003, Office XP Multilingual User Interface Packs, Office 2003 
Multilingual User Interface Packs and Exchange 2000 Server. MBSA 2.0 can detect 
security updates for products that Microsoft Update supports. For more 
information about MBSA, visit the MBSA Web site.

MBSA 2.0 does not support the detection of Exchange 5.0 Server, Office 2000, 
Office 2000 MultiLanguage Packs or Office 2003 Language Interface Packs. 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.

Can I use Systems Management Server (SMS) to determine whether this update is 
required?
Yes. SMS can help detect and deploy this security update. However, SMS uses 
MBSA for detection; therefore, SMS has the same limitation listed earlier in 
this bulletin related to programs that MBSA does not detect.

SMS can also use the Microsoft Office Inventory Tool to detect required updates 
for Microsoft Office applications
The Security Update Inventory Tool can be used by SMS for detecting security 
updates that are offered by Windows Update, that are supported by Software 
Update Services, and for detecting other security updates that are supported by 
MBSA 1.2.1. 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 2003 Inventory Tool for Microsoft Updates can be used by SMS for 
detecting 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, see the following Microsoft Web site.
SMS can also use the Microsoft Office Inventory Tool to detect required updates 
for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
Top of section
Vulnerability Details

TNEF Decoding Vulnerability - CVE-2006-0002

A remote code execution vulnerability exists in Microsoft Outlook and Microsoft 
Exchange Server because of the way that it decodes the Transport Neutral 
Encapsulation Format (TNEF) MIME attachment.
An attacker could exploit the vulnerability by constructing a specially crafted 
TNEF message that could potentially allow remote code execution when a user 
opens or previews a malicious e-mail message or when the Microsoft Exchange 
Server Information Store processes the specially crafted message.
An attacker who successfully exploited this vulnerability could take complete 
control of an affected system.
Mitigating Factors for TNEF Decoding Vulnerability - CVE-2006-0002:

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

Top of section
Workarounds for TNEF Decoding Vulnerability - CVE-2006-0002:

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.
âBlock MS-TNEF on Microsoft Exchange Server to help protect against attempts 
to exploit this vulnerability through SMTP e-mail.
Systems can be configured to block certain types of files from being received 
as e-mail attachments. Microsoft TNEF-encoded e-mail messages, commonly known 
as rich text format (RTF) e-mail messages, can contain malicious OLE objects. 
These e-mail messages contain a file attachment that stores the TNEF 
information. This file attachment is usually named Winmail.dat. Blocking this 
file, and blocking the ms-tnef MIME type, could help protect Exchange servers 
and other affected programs from attempts to exploit this vulnerability if 
customers cannot install the available security update. To help protect an 
Exchange Server computer from attacks through SMTP, block the Winmail.dat file 
and all application/ms-tnef MIME type content before it reaches the Exchange 
Server computer.

Note You cannot mitigate this vulnerability by setting the Exchange rich-text 
format option in Exchange Server to Never used or by disabling TNEF processing 
by editing the registry.

Note Exchange supports other messaging protocols, such as X.400, that these 
workarounds do not protect. We recommend that administrators require 
authentication on all other client and message transport protocols to help 
prevent attacks using these protocols.

Note Filtering only for attachments that have the file name Winmail.dat may not 
be sufficient to help protect your system. A malicious file attachment could be 
given another file name that could then be processed by the Exchange Server 
computer. To help protect against malicious e-mail messageâs, block all 
application/ms-tnef MIME type content.

There are many ways to block the Winmail.dat file and other TNEF content. Here 
are some suggestions:
âYou can use ISA Server 2000 SMTP Message Screener to block all file 
attachments or to block only the Winmail.dat file. Blocking all file 
attachments provides the most protection for this issue if you use ISA Server 
2000 because ISA Server 2000 does not support blocking content based on MIME 
content types. For more information, see Microsoft Knowledge Base Article 
315132.
âYou can use ISA Server 2000 SMTP Filter to block all file attachments or to 
block only the Winmail.dat file. Blocking all file attachments provides the 
most protection for this issue if you use ISA Server 2000 because ISA Server 
2000 does not support blocking content based on MIME content types. For more 
information, see Microsoft Knowledge Base Article 320703.
âYou can use ISA Server 2004 SMTP Filter and Message Screener block all file 
attachments or just the Winmail.dat file. Blocking all file attachments 
provides the most protection for this issue if you use ISA Server 2004 because 
ISA Server 2004 does not support blocking content based on MIME content types. 
For more information, see Microsoft Knowledge Base Article 888709.
âYou can use third-party e-mail filters to block all application/ms-tnef MIME 
type content before it is sent to the Exchange Server computer or to a 
vulnerable application.

Impact of workaround: If TNEF attachments are blocked, e-mail messages that are 
formatted as RTF will not be received correctly. In some cases, users could 
receive blank e-mail messages instead of the original RTF-formatted e-mail 
message. In other cases, users may not receive e-mail messages that are 
formatted as RTF at all. Blocking the TNEF attachments will not affect e-mail 
messages that are formatted as HTML or that are formatted as plain text. 
Perform this workaround only if you cannot install the available security 
update or if a security update is not publicly available for your configuration.
âRequire authentication for connections to a server that is running Microsoft 
Exchange Server for all client and message transport protocols.
Requiring authentication for all connections made to the Exchange Server 
computer will help protect against anonymous attacks. This will not protect 
against an attack from a malicious user who can successfully authenticate.

Impact of workaround: Anonymous communication from clients through IMAP, POP3, 
HTTP, LDAP, SMTP, and NNTP will no longer be possible. Server to server 
anonymous communication through RPC, X.400, foreign gateway, and third-party 
connector protocols will also no longer be possible. In most configurations of 
Exchange Server, authenticated access is already required for all protocols 
except SMTP. If all application/ms-tnef MIME type message parts and the 
Winmail.dat file are blocked, as described in the previous workaround, 
anonymous SMTP connections could still be accepted.
âDo not accept incoming public newsfeeds through the NNTP protocol on 
Microsoft Exchange Server.
Incoming newsfeeds are not enabled by default for Exchange Server. If you have 
subscribed to incoming newsfeeds from public newsgroups, an attacker could post 
a malicious message to such a newsgroup. Even if you require authentication 
between the news server and your Exchange Server computer, such a message could 
still be transferred to your Exchange Server computer. Therefore, you should 
disable incoming newsfeeds from any NNTP server that could let a user post a 
malicious message.

Impact of workaround: Exchange access to public newsgroup feeds will no longer 
be possible.

Top of section
FAQ for TNEF Decoding Vulnerability - CVE-2006-0002:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully 
exploited this vulnerability could take complete control of an affected system. 
An attacker could then install programs; view, change, or delete data; or 
create new accounts with full user rights. 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.
What causes the vulnerability?
Microsoft Exchange Server and Outlook both use the TNEF protocol. The 
vulnerability lies in the fact that Outlook or Exchange decodes a specially 
formed e-mail message that uses the TNEF protocol.
What is TNEF?
Transport Neutral Encapsulation (TNEF) is a format used by the Microsoft 
Exchange Server and Outlook e-mail clients when sending messages formatted as 
Rich Text Format (RTF). When Microsoft Exchange thinks that it is sending a 
message to another Microsoft e-mail client, it extracts all the formatting 
information and encodes it in a special TNEF block. It then sends the message 
in two parts - the text message with the formatting removed and the formatting 
instructions in the TNEF block. On the receiving side, a Microsoft e-mail 
client processes the TNEF block and re-formats the message
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete 
control of the affected system.
Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to a user who 
is running Outlook or Exchange Server could try to exploit this vulnerability.
What systems are primarily at risk from the vulnerability?
Workstations and Microsoft Exchange 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.
What does the update do?
The update removes the vulnerability by modifying the way that Outlook and 
Microsoft Exchange Server validate the length of a message before it passes the 
message to the allocated buffer.
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.
Top of section
Top of section
Top of section
Security Update Information

Affected Software:
For information about the specific security update for your affected software, 
click the appropriate link:
Outlook 2000 and Office 2000 MultiLanguage Packs

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 2000 Service Pack 3 (SP3), Microsoft Works 2000, or Microsoft Works 
2001 must be installed. In addition, if you are installing Office 2000 
Multilingual User Interface Packs, you must install Office 2000 Multilingual 
User Interface Packs Service Pack 3 (SP3). For additional information about how 
to install Office 2000 SP3, see Microsoft Knowledge Base Article 326585.

For additional information about how to determine the version of Office 2000 
that is installed on your computer, see Microsoft Knowledge Base Article 255275.
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.
Top of section
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.
Top of section
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
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user.
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes 
to the user.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you 
are prompted for a target folder.
/c:pathOverride install command defined by author. Specifies the path and name 
of the Setup.inf or .exe file.
/r:nNever restarts the computer after installation.
/r:IPrompts the user to restart the computer if a restart is required, except 
when used with /q:a.
/r:aAlways restarts the computer after installation.
/r:sRestarts the computer after installation without prompting the user.
/n:vNo 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 additional information about the supported setup switches, see Microsoft 
Knowledge Base Article 197147.
Client Deployment Information 
1.Download the client version of this security update.
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.
Outlook 2000:
File NameVersionDateTimeSize
Cdo.dll5.5.2657.7918-Nov-200323:40720,656
Cdo.dll_00045.5.2657.7918-Nov-200323:40813,840
Contab32.dll_00029.0.0.871823-Mar-200423:36127,027
Emsabp32.dll_00055.5.3189.009-May-200320:10154,112
Emsmdb32.dll_00055.5.3190.029-Sep-200319:36594,192
Emsui32.dll_00055.5.3188.009-May-200320:10131,344
Exsec32.dll_00055.5.3196.008-Apr-200401:33545,040
Msmapi32.dll_00015.5.3201.022-Sep-200520:15796,672
Msmapi32.dll_00025.5.3201.022-Sep-200520:09627,200
Olkfstub.dll9.0.0.730303-Jan-200322:1553,298
Omi9.dll_00015.5.3201.022-Sep-200520:09458,240
Omint.dll_00015.5.3201.022-Sep-200520:15552,448
Omipst9.dll_00015.5.3199.008-Feb-200520:10474,624
Omipstnt.dll_00015.5.3199.008-Feb-200520:17550,912
Outex.dll8.30.3197.018-May-200422:23782,608
Pstprx32.dll_00029.0.6718.023-Jul-200220:41368,691

Office 2000 MultiLanguage Packs:
File NameVersionDateTimeSize
Emsabp32.dll_0005_eng5.5.3189.009-May-200320:10154,112
Emsui32.dll_0005_eng5.5.3188.009-May-200320:10131,344
Exsec32.dll_0005_eng5.5.3187.017-Jan-200323:36540,944
Msmapi32.dll_0001_eng5.5.3201.022-Sep-200520:15796,672
Msmapi32.dll_0002_eng5.5.3201.022-Sep-200520:09627,200
Omi9.dll_0001_eng5.5.3201.022-Sep-200520:09458,240
Omint.dll_0001_eng5.5.3201.022-Sep-200520:15552,448
Omipst9.dll_0001_eng5.5.3199.008-Feb-200520:10474,624
Omipstnt.dll_0001_eng5.5.3199.008-Feb-200520:17550,912
Outex.dll_eng8.30.3173.023-Jul-200220:47782,608
Pstprx32.dll_0002_eng9.0.6718.023-Jul-200220:41368,691

Verifying that the Update Has Been Applied
âMicrosoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be 
able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows 
administrators to scan local and remote systems for missing security updates 
and for common security misconfigurations. For more information about MBSA, 
visit the Microsoft Baseline Security Analyzer Web site.
âFile Version Verification
Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.
1.Click Start, and then click Search.
2.In the Search Results pane, click All files and folders under Search 
Companion.
3.In the All or part of the file name box, type a file name from the 
appropriate file information table, and then click Search.
4.In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties.

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

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


Top of section
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.
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you 
are prompted for a target folder.
/c:pathOverrides the install command that is defined by author. Specifies the 
path and name of the Setup.inf or .exe file.

For additional information about the supported setup switches, see Microsoft 
Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, perform the following procedure:
1.Download the administrative version of this security update.
2.Click Save this program to disk, and then click Save again.
3.Using Windows Explorer, locate the folder that contains the saved file and 
run the following command line 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.
1.Click Yes to accept the License Agreement.
2.Click Yes if you are prompted to create the folder.
3.If you are familiar with the procedure for updating your administrative 
installation, click Start, and then click Run. Type the following command in 
the Open box:

msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE
Where 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.
1.Click Next in the provided dialog box. Do not change your CD Key, 
installation location, or company name in the provided dialog box.
2.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 that were originally installed from this 
administrative installation. To do this, please review the Workstation 
Deployment section. Any new installations that you run from this administrative 
installation point will include the update.
Warning Any workstation 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 section for this workstation.
Workstation Deployment Information 
To deploy the update to the client workstations, click Start, and then click 
Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
Where 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.
ProductFeature
Microsoft Outlook 
2000OutlookCDO,OutlookMAPICONTAB,OutlookMAPIEMS,OutlookMessaging,OutlookMAPI,OUTLOOKNonBootFiles,OutlookOMI

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 additional 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.
Outlook 2000:
File NameVersionDateTimeSize
Cdo.dll5.5.2657.7918-Nov-200323:40720,656
Cdo.dll_00045.5.2657.7918-Nov-200323:40813,840
Contab32.dll_00029.0.0.871823-Mar-200423:36127,027
Emsabp32.dll_00055.5.3189.009-May-200320:10154,112
Emsmdb32.dll_00055.5.3190.029-Sep-200319:36594,192
Emsui32.dll_00055.5.3188.009-May-200320:10131,344
Exsec32.dll_00055.5.3196.008-Apr-200401:33545,040
Msmapi32.dll_00015.5.3201.022-Sep-200520:15796,672
Msmapi32.dll_00025.5.3201.022-Sep-200520:09627,200
Olkfstub.dll9.0.0.730303-Jan-200322:1553,298
Omi9.dll_00015.5.3201.022-Sep-200520:09458,240
Omint.dll_00015.5.3201.022-Sep-200520:15552,448
Omipst9.dll_00015.5.3199.008-Feb-200520:10474,624
Omipstnt.dll_00015.5.3199.008-Feb-200520:17550,912
Outex.dll8.30.3197.018-May-200422:23782,608
Pstprx32.dll_00029.0.6718.023-Jul-200220:41368,691

Office 2000 MultiLanguage Packs:
File NameVersionDateTimeSize
Emsabp32.dll_0005_eng5.5.3189.009-May-200320:10154,112
Emsui32.dll_0005_eng5.5.3188.009-May-200320:10131,344
Exsec32.dll_0005_eng5.5.3187.017-Jan-200323:36540,944
Msmapi32.dll_0001_eng5.5.3201.022-Sep-200520:15796,672
Msmapi32.dll_0002_eng5.5.3201.022-Sep-200520:09627,200
Omi9.dll_0001_eng5.5.3201.022-Sep-200520:09458,240
Omint.dll_0001_eng5.5.3201.022-Sep-200520:15552,448
Omipst9.dll_0001_eng5.5.3199.008-Feb-200520:10474,624
Omipstnt.dll_0001_eng5.5.3199.008-Feb-200520:17550,912
Outex.dll_eng8.30.3173.023-Jul-200220:47782,608
Pstprx32.dll_0002_eng9.0.6718.023-Jul-200220:41368,691

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


Top of section
Top of section
Outlook 2002 and Office XP Multilingual User Interface Packs

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. In addition, if you are installing Office XP 
Multilingual User Interface Packs, you must install Multilingual User Interface 
Packs Service Pack 3 (SP3). For additional information about how to install 
Office XP SP3, see Microsoft Knowledge Base Article 832671.

For additional information about how to determine the version of Office XP that 
is installed on your computer, see Microsoft Knowledge Base Article 291331. For 
additional information about the version information displayed in the About 
dialog box, see Microsoft Knowledge Base Article 328294.
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.
Top of section
Automated Client Installation Information

Office 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.
Top of section
Manual Client Installation Information

For detailed information about how to manually install this update please 
review the following section.
Installation Information 
The security update supports the following setup switches:
Supported Security Update Installation Switches
SwitchDescription
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes 
to the user
/t:pathSpecifies the target folder for extracting files
/cExtracts the files without installing them. If /t:path is not specified, you 
are prompted for a target folder
/c:pathOverride install command defined by author. Specifies the path and name 
of the Setup.inf or .exe file
/r:nNever restarts the computer after installation.
/r:IPrompts the user to restart the computer if a restart is required, except 
when used with /q:a
/r:aAlways restarts the computer after installation
/r:sRestarts the computer after installation without prompting the user
/n:vNo 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 additional information about the supported setup switches, see Microsoft 
Knowledge Base Article 197147.
Client Deployment Information 
1.Download the client version of this security update.
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.
Outlook 2002:
File NameVersionDateTimeSize
Cdo.dll_00015.5.2658.718-May-200420:00727,504
Cdo.dll_00045.5.2658.2914-Jan-200503:02817,424
Contab32.dll10.0.6774.028-Aug-200503:15133,832
Emablt32.dll10.0.6713.005-May-200403:47113,352
Emsabp32.dll_000510.0.6752.017-Feb-200503:28199,368
Emsmdb32.dll_000510.0.6742.028-Nov-200407:04539,336
Emsui32.dll_000510.0.6308.013-Oct-200322:03129,592
Msmapi32.dll_000110.0.6772.016-Aug-200523:57862,920
Mspst32.dll_000410.0.6515.017-Dec-200321:32535,240
Olkfstub.dll10.0.6515.017-Dec-200321:3156,008
Outex.dll10.0.6770.014-Jul-200506:06744,128
Outllibr.dll10.0.6711.008-Apr-200402:241,977,032
Pstprx32.dll10.0.6308.013-Oct-200322:04338,496

Office XP Multilingual User Interface Pack
File NameVersionDateTimeSize
Contab32.dll10.0.6774.028-Aug-200503:15133,832
Emablt32.dll10.0.6713.005-May-200403:47113,352
Emsabp32.dll_000510.0.6752.017-Feb-200503:28199,368
Emsmdb32.dll_000510.0.6742.028-Nov-200407:04539,336
Emsui32.dll_000510.0.6308.013-Oct-200322:03129,592
Msmapi32.dll_000110.0.6772.016-Aug-200523:57862,920
Mspst32.dll_000410.0.6515.017-Dec-200321:32535,240
Outex.dll10.0.6770.014-Jul-200506:06744,128
Outllibr.dll10.0.6711.008-Apr-200402:241,977,032
Pstprx32.dll10.0.6308.013-Oct-200322:04338,496

Verifying that the Update Has Been Applied
âMicrosoft Baseline Security Analyzer
To verify that a security update is installed on an affected system you may be 
able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows 
administrators to scan local and remote systems for missing security updates 
and for common security misconfigurations. For more information about MBSA, 
visit the Microsoft Baseline Security Analyzer Web site.
âFile Version Verification
Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.
1.Click Start, and then click Search.
2.In the Search Results pane, click All files and folders under Search 
Companion.
3.In the All or part of the file name box, type a file name from the 
appropriate file information table, and then click Search.
4.In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties.

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

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


Top of section
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.
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you 
are prompted for a target folder.
/c:pathOverride install command defined by author. Specifies the path and name 
of the Setup.inf or .exe file.

For additional information about the supported setup switches, see Microsoft 
Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, perform the following procedure:
1.Download the administrative version of this security update.
2.Click Save this program to disk, and then click Save again.
3.Using Windows Explorer, locate the folder that contains the saved file and 
run the following command line 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.
1.Click Yes to accept the License Agreement.
2.Click Yes if you are prompted to create the folder.
3.If you are familiar with the procedure for updating your administrative 
installation, click Start, and then click Run. Type the following command in 
the Open box:

msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE
Where 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, PRO.msi), and MSP File is the name of the 
administrative update (for example, OLKINTLff.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.
1.Click Next in the provided dialog box. Do not change your CD Key, 
installation location, or company name in the provided dialog box.
2.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 that were originally installed from this 
administrative installation. To do this, please review the Workstation 
Deployment section. Any new installations that you run from this administrative 
installation point will include the update.
Warning Any workstation 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 section for this workstation.
Workstation Deployment Information 
To deploy the update to the client workstations, click Start, and then click 
Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
Where 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, PRO.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
Microsoft Outlook 
2002OutlookCDO,OutlookMAPICONTAB2,OutlookMAPILDAP2,OutlookMAPIEMS2,OutlookMAPI2,OutlookMAPIPST2,OUTLOOKNonBootFiles,OutlookMessaging,OUTLOOKFiles

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 additional 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.
Outlook 2002:
File NameVersionDateTimeSize
Cdo.dll_00015.5.2658.718-May-200420:00727,504
Cdo.dll_00045.5.2658.2914-Jan-200503:02817,424
Contab32.dll10.0.6774.028-Aug-200503:15133,832
Emablt32.dll10.0.6713.005-May-200403:47113,352
Emsabp32.dll_000510.0.6752.017-Feb-200503:28199,368
Emsmdb32.dll_000510.0.6742.028-Nov-200407:04539,336
Emsui32.dll_000510.0.6308.013-Oct-200322:03129,592
Msmapi32.dll_000110.0.6772.016-Aug-200523:57862,920
Mspst32.dll_000410.0.6515.017-Dec-200321:32535,240
Olkfstub.dll10.0.6515.017-Dec-200321:3156,008
Outex.dll10.0.6770.014-Jul-200506:06744,128
Outllibr.dll10.0.6711.008-Apr-200402:241,977,032
Pstprx32.dll10.0.6308.013-Oct-200322:04338,496

Office XP Multilingual User Interface Pack:
File NameVersionDateTimeSize
Contab32.dll10.0.6774.028-Aug-200503:15133,832
Emablt32.dll10.0.6713.005-May-200403:47113,352
Emsabp32.dll_000510.0.6752.017-Feb-200503:28199,368
Emsmdb32.dll_000510.0.6742.028-Nov-200407:04539,336
Emsui32.dll_000510.0.6308.013-Oct-200322:03129,592
Msmapi32.dll_000110.0.6772.016-Aug-200523:57862,920
Mspst32.dll_000410.0.6515.017-Dec-200321:32535,240
Outex.dll10.0.6770.014-Jul-200506:06744,128
Outllibr.dll10.0.6711.008-Apr-200402:241,977,032
Pstprx32.dll10.0.6308.013-Oct-200322:04338,496

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


Top of section
Top of section
Outlook 2003 and Office 2003 Multilingual User Interface Packs:

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 2003 Service Pack 2 or the Microsoft Office 2003 Multilingual User 
Interface Packs Service Pack 2 must be installed. Before you install this 
update, install Office 2003 SP2. In addition, if you are installing Office 2003 
Multilingual User Interface Packs, you must install Multilingual User Interface 
Packs Service Pack 2 (SP2). For additional information about how to install 
Office 2003 Service Pack 2, see Microsoft Knowledge Base Article 887616. The 
administrative update can also be installed on systems that are running the 
version of Office 2003 Service Pack 1.

For additional information about how to determine the version of Office 2003 
that is installed on your computer, see Microsoft Knowledge Base Article 
821549. For additional 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 the Add or Remove Programs tool 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 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.
Top of section
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.
Top of section
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.
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you 
are prompted for a target folder.
/c:pathOverride install command defined by author. Specifies the path and name 
of the Setup.inf or .exe file.

For additional information about the supported setup switches, see Microsoft 
Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation, perform the following procedure:
1.Download the administrative version of this security update.
2.Click Save this program to disk, and then click Save again.
3.Using Windows Explorer, locate the folder that contains the saved file and 
run the following command line 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.
1.Click Yes to accept the License Agreement.
2.Click Yes if you are prompted to create the folder.
3.If you are familiar with the procedure for updating your administrative 
installation, click Start, and then click Run. Type the following command in 
the Open box:

msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE
Where 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, PRO11.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.
1.Click Next in the provided dialog box. Do not change your CD Key, 
installation location, or company name in the provided dialog box.
2.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 that were originally installed from this 
administrative installation. To do this, please review the Workstation 
Deployment section. Any new installations that you run from this administrative 
installation point will include the update.
Warning Any workstation 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 section for this workstation.
Workstation Deployment Information 
To deploy the update to the client workstations, click Start, and then click 
Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
Where 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, PRO11.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
Microsoft Outlook 2003 
OUTLOOKFiles,OUTLOOKNonBootFiles,OutlookDVExtensionsFiles,OutlookVBScript,OutlookDVSchplusinterFiles,OutlookDVSchplusFiles,OutlookImportExportFiles,OutlookCDO,OutlookMAPICONTAB2,OutlookMAPIEMS2,OutlookMAPILDAP2,OutlookMAPI2,OUTLOOKNonBootFiles,OutlookMAPIPST2,OutlookMessaging,OUTLOOKFiles

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 additional 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.
Outlook 2003:
File NameVersionDateTimeSize
Addrpars.dll11.0.6550.017-Mar-200521:3288,264
Dlgsetp.dll11.0.6550.017-Mar-200521:3277,000
Envelope.dll11.0.6551.025-Mar-200523:27132,296
Exchcsp.dll_000111.0.6424.001-Mar-200521:27247,808
Exsec32.dll_000111.0.8000.022-Oct-200523:15346,824
Impmail.dll11.0.6550.017-Mar-200521:32122,056
Oladd.fae11.0.6550.017-Mar-200521:41158,912
Olappt.fae11.0.6550.017-Mar-200521:41152,264
Oljrnl.fae11.0.6550.017-Mar-200521:41117,960
Olmail.fae11.0.6550.017-Mar-200521:41113,352
Olnote.fae11.0.6550.017-Mar-200521:41104,648
Oltask.fae11.0.6550.017-Mar-200521:41147,144
Outllib.dll11.0.8002.010-Nov-200520:027,614,664
Outlmime.dll11.0.6555.025-Apr-200520:2992,360
Outlook.exe11.0.8000.022-Oct-200523:15196,296
Outlph.dll11.0.6550.017-Mar-200521:32141,000
Outlrpc.dll11.0.6552.031-Mar-200520:2164,200
Outlvbs.dll_000111.0.6550.017-Mar-200521:3244,744
Sc2.sam11.0.6550.017-Mar-200521:41111,808
Schplus.sam11.0.6550.017-Mar-200521:41143,048
Transmgr.dll11.0.8000.022-Oct-200523:56100,552
Cdo.dll_0004_10336.5.7233.4821-Sep-200521:27735,424
Contab32.dll_103311.0.6550.017-Mar-200521:32116,424
Dumpster.dll_103311.0.6550.017-Mar-200521:3231,944
Emablt32.dll_103311.0.6550.017-Mar-200521:32106,696
Emsabp32.dll_0005_103311.0.6550.017-Mar-200521:32264,392
Emsmdb32.dll_0005_103311.0.8000.022-Oct-200523:15705,224
Emsui32.dll_0005_103311.0.8000.022-Oct-200523:15132,296
Mapir.dll_103311.0.6550.017-Mar-200521:32778,944
Mlshext.dll_103311.0.6550.017-Mar-200521:0930,408
Msmapi32.dll_0001_103311.0.8002.010-Nov-200520:011,414,344
Mspst32.dll_0004_103311.0.8001.001-Nov-200522:58724,680
Outex.dll_103311.0.8000.022-Oct-200523:15654,528
Outllibr.dll_103311.0.6565.005-Jul-200519:143,057,864
Pstprx32.dll_103311.0.8000.022-Oct-200523:15280,264
Scanpst.exe_0002_103311.0.6802.005-Oct-200504:5142,696
Scnpst32.dll_103311.0.6555.025-Apr-200520:29232,648
Scnpst64.dll_103311.0.6555.025-Apr-200520:29241,352

Office 2003 Multilingual User Interface Packs:
File NameVersionDateTimeSize
Contab32.dll_103311.0.6550.017-Mar-200521:32116,424
Dumpster.dll_103311.0.6550.017-Mar-200521:3231,944
Emablt32.dll_103311.0.6550.017-Mar-200521:32106,696
Emsabp32.dll_0005_103311.0.6550.017-Mar-200521:32264,392
Emsmdb32.dll_0005_103311.0.6555.025-Apr-200520:29704,712
Emsui32.dll_0005_103311.0.6555.025-Apr-200520:30132,296
Mapir.dll_103311.0.6550.017-Mar-200521:32778,944
Msain.dll_103311.0.6565.005-Jul-200519:09589,504
Msmapi32.dll_0001_103311.0.6572.030-Aug-200520:261,414,856
Msointl.dll_103311.0.6565.005-Jul-200519:221,751,240
Mspst32.dll_0004_103311.0.6566.007-Jul-200523:59723,656
Outex.dll_103311.0.6555.025-Apr-200520:29653,504
Outllibr.dll_103311.0.6565.005-Jul-200519:143,057,864
Owci10.dll_103310.0.6765.003-Jun-200507:36506,568
Pstprx32.dll_103311.0.6550.017-Mar-200521:32279,240
Scanpst.exe_0002_103311.0.6565.005-Jul-200519:1342,696
Wwintl.dll_103311.0.6565.005-Jul-200519:08771,784
Xlintl32.dll_103311.0.6565.005-Jul-200519:17707,784

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


Top of section
Top of section
Office 2003 Language Interface Packs

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 2003 Service Pack 2 must be installed. Before you install this 
update, install Office 2003 SP2. For additional information about how to 
install Office 2003 Service Pack 2, see Microsoft Knowledge Base Article 887616.
âFor additional information about how to determine the version of Office 2003 
that is installed on your computer, see Microsoft Knowledge Base Article 
821549. For additional information about the version information displayed in 
the About dialog box, see Microsoft Knowledge Base Article 328294.

Removal Information
There is no option to remove this service pack by using Add or Remove Programs 
in Control Panel. To remove Office 2003 Service Pack 2 for Language Interface 
Pack, you must remove Office 2003. Then, you must reinstall Office 2003 from 
your original Office 2003 CD. For more information, click the following article 
number to view the article in the Microsoft Knowledge Base 873125
Top of section
Installation Information

For detailed information about how to manually install this update please 
review the following section.
Installation Information:
To download Office 2003 Service Pack 2 for Language Interface Pack, select your 
language and follow the instructions in the âInstallation Instructionsâ 
section.
Note: This download is not available in English.

See Microsoft Knowledge Base article (887617): Description of Office 2003 
Service Pack 2 for Language Interface Pack for further information about this 
update.
Top of section
Top of section
Exchange Server 5.0 Service Pack 2

Prerequisites 
This security update requires Exchange Server 5.0 Service Pack 2.
Installation Information: 
For additional information about the command options that you can use to apply 
this update, see Microsoft Knowledge Base article 257946:
257946 XGEN: GUI Hotfix Utility Switches /x /m /s /z
Deployment Information 
To install the security update without any user intervention, use the following 
command line:
Exchange5.0-KB894689-x86-enu /s
Restart Requirement:
All Exchange services will be stopped to apply this hotfix and will be 
restarted before finishing. After the installation is complete, verify that all 
necessary Exchange services have been restarted.
System managers should therefore carefully plan applying this update to cause 
minimal impact on normal operations.
Removal Information:
To remove this update, use the Add or Remove Programs tool in Control Panel or 
click Start, click Run, type the following command, and then click OK:
%exchsrvr%\894689\uninstall\uninst.exe
File Information:
The English version of this fix has the file attributes (or later) 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.
File NameVersionDateTimeSize
Mdbmsg.dll5.0.1462.2210-May-200519:12451,856
Store.exe5.0.1462.2210-May-200519:172,476,816

Verifying that the Update Has Been Applied
âMicrosoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you 
can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows 
administrators to scan local and remote systems for missing security updates 
and for common security misconfigurations. For more information about MBSA, 
visit the Microsoft Baseline Security Analyzer Web site.
âFile Version Verification
Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.
1.Click Start, and then click Search.
2.In the Search Results pane, click All files and folders under Search 
Companion.
3.In the All or part of the file name box, type a file name from the 
appropriate file information table, and then click Search.
4.In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties.

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

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

âRegistry Key Verification
You may also be able to verify the files that this security update has 
installed by reviewing the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Exchange Server 5.0\SP3\894689
Note This registry key may not contain a complete list of installed files. 
Also, this registry key may not be created correctly if an administrator or an 
OEM integrates or slipstreams the 894689 security update into the Windows 
installation source files.

Top of section
Exchange Server 5.5 Service Pack 4

Prerequisites: 
This security update requires Exchange Server 5.5 Service Pack 4.
Installation Information: 
For additional information about the command options that you can use to apply 
this update, see Microsoft Knowledge Base article 257946:
257946 XGEN: GUI Hotfix Utility Switches /x /m /s /z
Deployment Information 
To install the security update without any user intervention, use the following 
command line:
Exchange5.5-KB894689-x86-enu /s
Restart Requirement:
This update does not require a restart. However, Microsoft Internet Information 
Services (IIS), the Exchange Store, and the Exchange System Attendant Services 
will restart when you install the update. System managers should therefore 
carefully plan applying this update to cause minimal impact on normal 
operations.
Removal Information:
To remove this update, use the Add or Remove Programs tool in Control Panel or 
click Start, click Run, type the following command, and then click OK:
%exchsrvr%\894689\uninstall\uninst.exe
File Information:
The English version of this fix has the file attributes (or later) 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.
File NameVersionDateTimeSize
Mapi32.dll5.5.2658.3414-Apr-200505:06882,960
Mdbmsg.dll5.5.2658.3414-Apr-200505:35496,400
Store.exe5.5.2658.3414-Apr-200505:352,639,120

Verifying that the Update Has Been Applied
âMicrosoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you 
can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows 
administrators to scan local and remote systems for missing security updates 
and for common security misconfigurations. For more information about MBSA, 
visit the Microsoft Baseline Security Analyzer Web site.
âFile Version Verification
Note Because there are several versions of Microsoft Windows, the following 
steps may be different on your computer. If they are, see your product 
documentation to complete these steps.
1.Click Start, and then click Search.
2.In the Search Results pane, click All files and folders under Search 
Companion.
3.In the All or part of the file name box, type a file name from the 
appropriate file information table, and then click Search.
4.In the list of files, right-click a file name from the appropriate file 
information table, and then click Properties.

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

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

âRegistry Key Verification
You may also be able to verify the files that this security update has 
installed by reviewing the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Exchange Server 5.5\SP5\894689
Note This registry key may not contain a complete list of installed files. 
Also, this registry key may not be created correctly if an administrator or an 
OEM integrates or slipstreams the 894689 security update into the Windows 
installation source files.

Top of section
Exchange 2000 Server Service Pack 3 with Update Rollup 870540

Prerequisites
Prerequisites:
This security update requires Exchange 2000 Server Service Pack 3 with the 
Exchange 2000 Server Post-Service Pack 3 (SP3) Update Rollup. For more 
information, see Microsoft Knowledge Base Article 870540. To download the 
prerequisite update, visit this Web site.
Inclusion in service packs: 
The update for this issue will be included in a future service pack or update 
rollup.
Installation Information: 
This security update supports the following setup switches.
Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes 
/passiveUnattended Setup mode. No user interaction is required, but 
installation status is displayed. If a restart is required at the end of Setup, 
a dialog box will be presented to the user with a timer warning that the 
computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other 
applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the 
computer will restart in x seconds. (The default setting is 30 seconds.) 
Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options 
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates the update into the Windows source files. These files 
are located at the path that is specified in the switch.
/extract[:path]Extracts files without starting the Setup program.
/EREnables extended error reporting.
/verboseEnables verbose logging. During installation, creates 
%Windir%\CabBuild.log. This log details the files that are copied. Using this 
switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward 
compatibility, the security update also supports the setup switches that the 
earlier version of the Setup program uses. For more information about the 
supported installation switches, see Microsoft Knowledge Base Article 262841. 
For more information about the Update.exe installer, visit the Microsoft 
TechNet Web site.
Deployment Information 
To install the security update without any user intervention, use the following 
command at a command prompt:
Exchange2000-KB894689-x86-enu /quiet
Restart Requirement:
No restart of the computer is required provided all applications are closed 
before installation (including applications opened through a terminal server 
session). However, the security update will restart the IIS, SMTP, and the 
Exchange Server Information Store Service. The File Transfer Protocol (FTP) and 
Network News Transfer Protocol (NNTP) services will also be affected.
System managers should therefore carefully plan applying this update to cause 
minimal impact on normal operations.
Removal Information:
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can use the Spuninst.exe utility to remove this security 
update. The Spuninst.exe utility is located in the 
%Windir%\$ExchUninstall894689$\Spuninst folder.
Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes 
/passiveUnattended Setup mode. No user interaction is required, but 
installation status is displayed. If a restart is required at the end of Setup, 
a dialog box will be presented to the user with a timer warning that the 
computer will restart in 30 seconds.
/quietQuiet mode. This is the same as unattended mode, but no status or error 
messages are displayed.
Restart Options 
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other 
applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the 
computer will restart in x seconds. (The default setting is 30 seconds.) 
Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplay a dialog box prompting the local user to allow a restart.
Special Options 
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

File Information:
The English version of this fix has the file attributes (or later) 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.
Exchange 2000 Server Service Pack 3:
File NameVersionDateTimeSize
Mapi32.dll6.0.6617.4716-Feb-200500:11745,472
Store.exe6.0.6617.4716-Feb-200501:184,706,304
Cdo.dll6.0.6617.4716-Feb-200500:13720,896
Mdbmsg.dll6.0.6617.4716-Feb-200500:252,338,816

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

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

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

âRegistry Key Verification
You may also be able to verify the files that this security update has 
installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Exchange Server 2000\SP4\KB894689

Note This registry key may not contain a complete list of installed files. 
Also, this registry key may not be created correctly when an administrator or 
an OEM integrates or slipstreams the KB894689 security update into the Windows 
installation source files.
Top of section
Top of section
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
âJohn Heasman and Mark Litchfield of NGS Software for reporting the TNEF 
Decoding Vulnerability - CVE-2006-0002

Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
âSecurity updates are available in 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 (January 10, 2006): Bulletin published.

Top of page

Other related posts:

  • » [THIN] Alert: Vulnerability in TNEF Decoding in Microsoft Outlook and Microsoft Exchange Could Allow Remote Code Execution (902412)