Microsoft Security Bulletin MS04-028

Executive Summary:

This update resolves a newly-discovered, privately reported vulnerability. A buffer overrun vulnerability exists in the processing of JPEG image formats that could allow remote code execution on an affected system. The vulnerability is documented in this bulletin in its own section.

If a user is logged on with administrator privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.

Microsoft recommends that customers apply the update immediately.

Severity Ratings and Vulnerability Identifier:

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.

Why was this security bulletin updated on December 14, 2004?
The bulletin has been updated to advise on the availability of additional updates that help address this vulnerability:

The MS04-028 Enterprise Update Scanning Tool has been updated to detect and deploy the stand alone security updates for the Microsoft .NET Framework version 1.0 Service Pack 2 and the Microsoft .NET Framework version 1.1 as well as the Microsoft Visual FoxPro 8.0 security update. The existing version of this tool supported the detection and deployment of the Microsoft .NET Framework version 1.0 Service Pack 3 and the Microsoft .NET Framework version 1.1 Service Pack 1. Now that the standalone security updates are available this tool has been updated to use the stand alone updates instead of the service pack updates. Customers who prefer the support of the service pack updates should continue to use the existing version of this tool. Since Windows Messenger is not considered to be vulnerable to any known or likely attack vectors, it has not been included in this update. For more information about the MS04-028 Enterprise Update Scanning Tool, see Microsoft Knowledge Base Article 886988.

Why was this security bulletin updated on October 12, 2004?
Microsoft Knowledge Base Article 833987 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 833987

After the release of the MS04-028 security bulletin, Microsoft became aware of an issue affecting customers deploying the Office XP, Visio 2002, and Project 2002 updates on Windows XP Service Pack 2 based systems. In some cases, this issue caused the security updates to appear to install correctly, when in fact they did not. This is an issue with the installer used in the security update. For more technical details on this issue, and the specific conditions that can cause the installation to fail, see Microsoft Knowledge Base Article 885876.

As a reminder, Windows XP Service Pack 2 already contains the security update addressing the vulnerability in the JPEG Parsing Engine that is supplied by the operating system. However, customers still need to successfully apply the security updates for Office XP, Visio 2002, and Project 2002 in order to be protected from this vulnerability when using these applications.

Microsoft has investigated this issue and has made available revised security updates for these applications to help ensure that they install successfully on Windows XP Service Pack 2 based systems. These revised security updates are available from Office Update and the Microsoft Download Center. Customers who have not yet applied the original version of these updates should visit Office Update to receive the revised updates. Enterprise customers who have not yet applied the original version of these update should obtain the revised updates from the Microsoft Download Center by using the download links provided in the Affected Software section of this security bulletin.

For customers who have already applied the original Office XP, Visio 2002, and Project 2002 updates and are using Windows XP Service Pack 2, any one of the following steps will correct the issue and properly apply the update:

Microsoft has also identified the Windows Journal Viewer as affected by this security vulnerability and has released an update for Windows 2000-based systems. See the following FAQs for more information about the update for the Windows Journal Viewer for Windows 2000-based systems.

As part of this update, Microsoft has also released the MS04-028 Enterprise Update Scanning Tool. Review the MS04-028 Enterprise Update Scanning Tool FAQ in this updated security bulletin for more information.

Why has Microsoft released an update for the Windows Journal Viewer on October 12, 2004?
The Windows Journal Viewer makes it possible for users who do not have a system running Windows XP Tablet PC Edition to view files that were created in Windows Journal on a Tablet PC. The Windows Journal Viewer is vulnerable to the security vulnerability discussed in this bulletin. However, when used on Windows XP based systems, the Windows Journal Viewer uses the operating system supplied version of the affected component. When the Windows XP operating system update is applied on Windows XP and Windows XP Service Pack 1 based systems the Windows Journal Viewer is no longer vulnerable to this issue. Windows XP Service Pack 2 is not vulnerable to this issue, therefore the Windows Journal Viewer when used on Windows XP Service Pack 2 based systems is not vulnerable to this issue. We have now released a security update for Windows Journal Viewer that will help protect Windows 2000-based systems that may have installed the Windows Journal Viewer.

Even if you have installed all of the previously available security updates on Windows 2000, if you have installed the Windows Journal Viewer, it is important that you also install this security update. Windows Update will offer this update only to Windows 2000-based systems that have installed the Windows Journal Viewer. If you are using Windows XP or have not installed the Windows Journal Viewer on Windows 2000, you do not need this security update. This program is not supported on Windows Server 2003. However, if it were installed on Windows Server 2003, it would also use the operating system version of the vulnerable component. If you are using this program on Windows Server 2003 make sure that you install the Windows Server 2003 security update.

What is GDI+?
GDI+ is a graphics device interface that provides two-dimensional vector graphics, imaging, and typography to applications and programmers.

Why are there several affected programs and components?
Windows XP, Windows XP Service Pack 1, and Windows Server 2003 provide an operating system version of the component that is vulnerable to this issue. Earlier versions of Windows did not provide an operating system version of this component. Therefore, when you install programs that require this functionality on earlier versions of Windows, this component is commonly installed. Typically, when these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they only use the version that is provided by the operating system, even if they install a copy of the vulnerable component.

The exceptions to this are Office XP, Visio 2002, Project 2002, Office 2003, Visio 2003, and Project 2003. To help make sure that JPEG images are processed consistently across all operating systems, these programs use their own version of the vulnerable component. This version of the vulnerable component is installed on all operating systems that are supported by these programs. If you have installed these programs, you must install the update for these programs. You must also install an operating system update if you use Windows XP, Windows XP Service Pack 1, or Windows Server 2003. Also, please review the following FAQ questions relating to exceptions for application developers and third-party applications.

If I use Windows XP Service Pack 2 and use any of the affected software, what should I do?
Windows XP Service Pack 2 does not contain a vulnerable version of the affected component. However, if you have installed any of the affected Office, Visio, or Project applications you should install the updates for those applications. The easiest way to address this vulnerability is to install the updates provided by Office Update. If you have not installed any of the affected Office, Visio, or Project applications you do not have to install any other security updates because the other affected software and affected components use the operating system version of the vulnerable component on Windows XP Service Pack 2. However, please review the following FAQ questions relating to exceptions for application developers and third-party applications. Also, as explained in the previous FAQ, there are cases when the original versions of the Office, Visio, and Project security updates may not have installed correctly. For more information, see Microsoft Knowledge Base Article 833987.

If I use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and use any of the affected software, what should I do?
If you have installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by both Windows Update and Office Update. If you have not installed any of the affected Office, Visio, or Project applications the easiest way to address this vulnerability is to install the updates provided by Windows Update. You do not have to install any other security updates because the other affected software and affected components use the operating system version of the component on Windows XP and Windows Server 2003. However, please review the following FAQ questions relating to exceptions for application developers and third-party applications.

If I use Windows 98, Windows 98 Second Edition (SE), Windows Millennium Edition (Me), Windows NT 4.0, or Windows 2000, what should I do?
By default, these operating systems do not natively provide a version of the vulnerable component and are not affected. However, the vulnerable component is installed on these non-affected operating systems when you install any of the software programs or components that are listed in the Affected Software and Affected Components sections of this bulletin.

If you have installed any of the affected programs or components, you should install the required security updates for those programs or components. For example, if you have Internet Explorer 6 Service Pack 1 and Office XP installed on your Windows 2000 system, you have to install the Internet Explorer 6 Service Pack 1 security update and the Office XP security update. If you have not installed any of the affected programs or components, you do not have to install any security updates.

If I use versions of Internet Explorer that are earlier than Internet Explorer 6 Service Pack 1, am I vulnerable to this issue?
Internet Explorer 5.01 Service Pack 3, Internet Explorer 5.01 Service Pack 4 on Windows 2000, and Internet Explorer 5.5 Service Pack 2 on Windows Me have been tested and they are not vulnerable.

Internet Explorer 6 is only supported when using Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Internet Explorer 6 on Windows XP, Windows XP Service Pack 1, and Windows Server 2003 uses the operating system version of the vulnerable component. When the Windows XP, Windows XP Service Pack 1, and Windows Server 2003 operating system update is installed, Internet Explorer 6 is not vulnerable. Windows XP Service Pack 2 includes Internet Explorer 6 Service Pack 2 and is not vulnerable to this issue. Internet Explorer 6 is no longer in support on other operating systems and may be vulnerable to this issue on those operating systems. Customers who do not use Windows XP, Windows XP Service Pack 1, or Windows Server 2003 and who use versions of Internet Explorer 6 that are earlier than Internet Explorer 6 Service Pack 1 should upgrade to Internet Explorer 6 Service Pack 1 and then install the Internet Explorer 6 Service Pack 1 security update provided in this security bulletin, or upgrade to Windows XP Service Pack 2 for Windows XP customers. To install Internet Explorer 6 Service Pack 1, visit the following Web site. For more information about the support lifecycle for Internet Explorer, visit the following Microsoft Support Lifecycle Web site.

If I use third-party applications that distribute the gdiplus.dll file, could I still be vulnerable even after I have installed all required Microsoft security updates?
Yes. There are cases where you might be vulnerable to this issue even after you install the required operating system update and the updates for programs or components that are listed in the Affected Software and Affected Components sections of this bulletin.

If the Gdiplus.dll file is installed on your system, you may have to install an update for that program. Not every program that installs this file is vulnerable to this issue because it may not use the Gdiplus.dll file to process JPEG images. Even when the third-party application uses the Gdiplus.dll file to process JPEG images it may not do so in a vulnerable way. For example if an application does not allow users to supply images for processing or performs additional validation on the images before processing, it may not be vulnerable. However, only the manufacturer of that program can make that determination. This could include, but is not limited to, third party applications that were developed using Visual Studio .NET 2002, Visual Studio .NET 2003, or the Microsoft .NET Framework 1.0 SDK Service Pack 2.

Additionally, Windows XP and Windows Server 2003 provide additional methods to help secure applications. These operating systems provide an operating system version of the affected component and can be centrally protected. This means that even if an application installs a version of the Gdiplus.dll file, that the application in most cases will use the operating system supplied version. The operating system version of Gdiplus.dll is updated when you install the appropriate operating system update and will protect most applications from this vulnerability.

However, it is possible for a developer or administrator to force an application to bypass the operating system supplied version of the Gdiplus.dll file and instead use a version that they supply. There are several ways that an application developer may design their application to not use the operating system version of the component. They might explicitly call a version of the component that they have provided, or they might use a side by side bypass feature to call their version of the affected component. This is not likely to be used in most circumstances. However, you may want to consider contacting the third-party application manufacturer for an updated version of their program, if they verify that their program uses any type of bypass feature. Steps to determine if your application is using the side by side bypass feature are located in Microsoft Knowledge Base Article 835322. To determine if your applications has explicitly called a version of the component that they supply we recommend that you contact the application manufacturer. It is important to note that the use of these types of features is generally rare and not recommended. For more information, see the MSDN Web site

Furthermore, in these cases you would only be vulnerable to this issue while using the affected program to process images. Installing the operating system update and the updates for the affected programs and components listed in this bulletin will help reduce the chance that you will be attacked from the most common attack vectors an attacker could use to exploit this vulnerability.

It is also important to note that you should install any available security updates instead of manually updating the affected component, if possible. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.

If I am a developer and use Visual Studio .NET 2002, Visual Studio .NET 2003, the Microsoft .NET Framework 1.0 SDK Service Pack 2, or the Microsoft Platform SDK Redistributable: GDI+ to develop applications, what should I do?

When these programs are installed on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 they use the operating system version of the vulnerable component. If you are using these programs on Windows XP, Windows XP Service Pack 1, or Windows Server 2003 make sure that you install the operating system version of the security update. If you are using these programs on other operating systems make sure that you install the update for these programs.

However, if you use these programs to create applications that distribute a version of the Gdiplus.dll file you need to install the appropriate security update based on the development tool you use, even if you have installed an available operating system update or are using Windows XP Service Pack 2. If you use the Gdiplus.dll file for JPEG processing you should consider updating your application to use the updated version of the Gdiplus.dll file. However as mentioned in the previous FAQ, your application may not be directly vulnerable to this issue. Also, you should make sure that you are not using any of the bypass features mentioned in the previous FAQ that could create vulnerabilities within your application.

Can I manually script and deploy the required security updates?
Yes. We have released Microsoft Knowledge Base Article 885885 to assist with the manual installation of some of the available security updates. This article does not provide instructions for the installation of all available security updates and is provided only as a guide in the creation of custom scripts.

Why was the security update for the Microsoft .NET Framework 1.0 and the Microsoft .NET Framework 1.1 initially provided in a Service Pack?

This issue does not affect customers who have already deployed the Microsoft .NET Framework 1.0 Service pack 3 (SP3) and the Microsoft .NET Framework 1.1 Service Pack 1 (SP1). These service packs, released prior to the release of this security bulletin, already contain the security update for this issue as well as other security changes for all reported customer issues found after the release of these software components. Therefore, we highly recommended that customers using the Microsoft .NET Framework 1.0 or the Microsoft .NET Framework 1.1 install these Service Packs for increased security not only for this vulnerability but also for all reported customer issues found after the release of the Microsoft .NET Framework.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
MBSA does detect if the update for this vulnerability is required for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003 for local computer scans. For detailed information about how MBSA detects Office updates, visit the following Web site. MBSA displays a note to indicate that certain operating system updates are required. MBSA does not currently support the detection of several of the programs that are listed in the Affected Software and Affected Components section of this security bulletin. For detailed information about the programs that MBSA currently does not detect, see Microsoft Knowledge Base Article 306460. If you have installed any of the programs that are listed in the Affected Software and Affected Components section of this security bulletin you may have to manually determine if you have to install the required update. For example, a Windows 2000 or Windows NT 4.0 system that has installed Internet Explorer 6 Service Pack 1 will need to install the Internet Explorer 6 Service Pack 1 security update and MBSA will not detect the missing update in these configurations. Also, MBSA cannot use the Office Detection Tool to scan remote systems, it will only use this tool to scan a system locally for required security updates. For more information about MBSA, visit the MBSA Web site.

Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2 from the MBSA Web site. For more information about MBSA support, visit the Microsoft Baseline Security Analyzer 1.2 Q&A Web site.

Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. However, SMS can also use the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office components.

Can I use SMS to determine if programs are installed that have to be updated?
Yes. SMS can help detect if any of the affected programs or affected components are installed that may have installed a version of the vulnerable component. SMS can search for the existence of the file Gdiplus.dll. For the affected programs and components listed in this bulletin may need to update all versions of Gdiplus.dll that are earlier than version 5.1.3102.1355 or versions that are identified as vulnerable in the following FAQ’s that are in use by affected applications. See the ‘If I use third-party applications that distribute the gdiplus.dll file, could I still be vulnerable even after I have installed all required Microsoft security updates?’ FAQ in this bulletin for more information about other applications that may have installed the Gdiplus.dll file.

However, it is important to note that you should install the available security updates instead of manually updating the affected component. Manually updating the affected component could create application compatibility issues and is not supported. Also, applications that feature ‘Detect and Repair’ functionality will not receive the necessary information required to prevent these features from potentially introducing the vulnerability upon execution if the affected component is manually updated.

Installations of Office XP, Visio 2002, Project 2002, and Internet Explorer 6 Service Pack 1 (SP1) combine the features of the vulnerable component with other files. For Office XP and Project 2002 you would also have to search for the existence of the Mso.dll file. Update versions of Mso.dll that are earlier than version 10.0.6714.0 that are in use by affected applications. For Visio 2002, you have to search for the existence of the Mso.dll file and the Gdiplus.dll file because Visio 2002 distributes both files, except on Windows XP, or Windows Server 2003 where it only distributes the Mso.dll file.

For installations of Internet Explorer 6 Service Pack 1 that are not running on the Windows XP or Windows Server 2003 operating systems, search for the Vgx.dll file. Update all versions of Vgx.dll that are earlier than version 6.0.2800.1411. Internet Explorer 6 Service Pack 1 uses the operating system version of the vulnerable component on Windows XP and Windows Server 2003. You do not have to update Internet Explorer 6 Service Pack 1 for those operating systems. These .dll files are documented in the Security Update Information section of this security bulletin. You can also deploy the updates provided in this bulletin using the Inventory and Software Distribution feature of SMS.

Which versions of the Gdiplus.dll file could cause applications to become vulnerable?
It is important to remember that the existence of the Gdiplus.dll file does not determine if an application is vulnerable to this issue. The previous FAQs can be used to help determine if you are using the Gdiplus.dll file as part of a vulnerable application. As a general guide to help administrators and developers determine if they are using a version of the Gdiplus.dll file that could allow their applications to become vulnerable to this issue, we have created the following Gdiplus.dll file information table.

Microsoft has released the MS04-028 Enterprise Update Scanning Tool that will assist enterprise customers in detecting if they are running one or more affected products and components, and help them deploy the available security updates. Where can I get more information about this tool?
In an effort to further support enterprise customers through the unique deployment complexities of MS04-28, due to the number of products and components affected, Microsoft has released a scanning tool and guidance that offers system administrators the ability to scan computers on their network for the software listed in the Affected Software and Affected Components sections of this security bulletin and to automatically apply the appropriate MS04-028 updates. The tool can also be used in conjunction with Microsoft’s System Management Server (SMS). For more information about the MS04-028 Enterprise Update Scanning Tool, see Microsoft Knowledge Base Article 886988. This tool does support the Windows Journal Viewer security update.

Microsoft has released the GDI+ Detection Tool for consumers that will also assist in detecting if you are running one or more affected products and components. Where can I get more information about this tool?

Microsoft has created the GDI+ Detection tool to assist consumers in detecting if they are running one or more affected versions of the software listed in the Affected Software and Affected Components sections of this security bulletin that contain a vulnerable version of the JPEG Parsing component on their system. Microsoft Knowledge Base Article 873374 describes this tool as well as provides instructions on how to download this tool. This tool has not been updated to support the Windows Journal Viewer security update.

What does the GDI+ Detection tool do?

The GDI+ Detection tool scans your system for non-operating system software listed in the Affected Software and Affected Components sections of this security bulletin that are known to contain the vulnerable component. It then directs consumers to the appropriate locations for downloading an update to address the vulnerability.

Will the GDI+ Detection tool tell me if my system is at risk from this vulnerability?

No. The tool is only designed to scan the system and detect for the software listed in the Affected Software and Affected Components sections of this security bulletin that are known to contain the vulnerable component. The tool is not able to determine if these products have already been updated to use a secure version of the affected component.

I use Software Update Services (SUS) to deploy security updates in my enterprise. Should I deploy the GDI+ Detection Tool to all of my systems?

The GDI+ Detection Tool was available via SUS but has been removed. This tool is not designed for use or supported in enterprise environments.

What security updates will Windows Update offer to help address this vulnerability?
Windows Update will offer the required operating system updates for Windows XP, Windows XP Service Pack 1, and Windows Server 2003. Windows XP Service Pack 2 does not require an update because it does not contain a vulnerable version of the affected component. Windows Update will offer the Internet Explorer 6 Service Pack 1 security update to Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems. Windows Update will offer the .NET Framework, version 1.0 Service Pack 3 (SP3) and the .NET Framework, version 1.1 Service Pack 1 to Windows NT 4.0 and Windows 2000 operating systems. Windows Update will offer an update for the Windows Journal Viewer only to Windows 2000-based systems that have installed the Windows Journal Viewer. These security updates are not offered to Windows XP or Windows Server 2003 systems because these operating system components and applications use the operating system version of the affected component on Window XP and Windows Server 2003.

Also, as explained in a previous FAQ, there are cases, when using Windows XP Service Pack 2, where the original versions of the Office XP, Visio 2002, and Project 2002 security updates may not have installed correctly. For these Windows XP Service Pack 2 customers, Microsoft has provided an updated installation package through Windows Update that will correct the installation problem and install the correct files. Since Windows XP Service Pack 2 recommends and prompts customers to turn Automatic Update on, most Windows XP Service Pack 2 users will not have to take any additional steps. This updated installation package is documented in Microsoft Knowledge Base Article 885884.

What security updates will Office Update offer to help address this vulnerability?
Office Update will offer the required updates for Office XP, Office 2003, Project 2002, Project 2003, Visio 2002, and Visio 2003. These security updates are required on all operating systems where these products are installed. Office 2003 Service Pack 1, Visio 2003 Service Pack 1, and Project 2003 Service Pack 1 are not affected and will be offered to customers using Office 2003, Project 2003, and Visio 2003 instead of the individual updates. Customers who have installed these service packs are not affected by this vulnerability from these applications.

What security updates will not be offered through Windows Update or Office Update to help address this vulnerability and should be manually installed?
Windows Update and Office Update do not provide support for the remaining programs. This includes the security updates for Visual Studio .NET 2002 (and all included programs), Visual Studio .NET 2003 (and all included programs), Greetings 2002, Picture It! (all versions), Digital Image (all versions), the Microsoft .NET Framework version 1.0 SDK Service Pack 2, the Microsoft .NET Framework version 1.0 Service Pack 2 standalone security update, the Microsoft .NET Framework version 1.1 standalone security update, Producer for Microsoft Office PowerPoint (all versions), and the Platform SDK Redistributable: GDI+. These security updates are required on Windows 98, Windows 98 SE, Windows Me, Windows NT 4.0 and Windows 2000 operating systems where these products are installed. Note Visual Studio .NET 2002 Enterprise Architect and Visual Studio .NET 2003 Enterprise Architect include Visio 2002. Visio 2002 is supported by Office Update.

Are the Visio 2002 Viewer, Visio 2003 Viewer, and PowerPoint 2003 Viewer programs affected by this vulnerability?
Earlier versions of the Visio 2002 Viewer, Visio 2003 Viewer, and PowerPoint 2003 Viewer programs are affected by this vulnerability. We do not offer security update support for these programs. However, the most recent version of the Visio 2002 Viewer, Visio 2003 Viewer, and PowerPoint 2003 Viewer programs are not affected by this vulnerability. We recommend that customers install the most recent version of these programs.

Installation Platforms and Prerequisites:

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

Prerequisites
This security update requires a released version of Windows Server 2003.

Inclusion in Future Service Packs:
The update for this issue will be included in Windows Server 2003 Service Pack 1.

Installation Information

This security update supports the following setup switches:

      /help                 Displays the command line options

Setup Modes

      /quiet              Quiet mode (no user interaction or display)

      /passive            Unattended mode (progress bar only)

      /uninstall          Uninstalls the package

Restart Options

      /norestart          Do not restart when installation is complete

      /forcerestart      Restart after installation

Special Options

      /l           Lists installed Windows hotfixes or update packages

      /o          Overwrite OEM files without prompting

      /n          Do not backup files needed for uninstall

      /f           Force other programs to close when the computer shuts down

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Deployment Information

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

   Windowsserver2003-kb833987-x86-enu /passive /quiet

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

   Windowsserver2003-kb833987-x86-enu /norestart

For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

In some cases, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB833987$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

   /?: Show the list of installation switches.

   /u: Use unattended mode.

   /f: Force other programs to quit when the computer shuts down.

   /z: Do not restart when the installation is complete.

   /q: Use Quiet mode (no user interaction).

File Information

The English version of this update 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.

Windows Server 2003 Enterprise Edition, Windows Server 2003 Standard Edition, Windows Server 2003 Web Edition, and Windows Server 2003 Datacenter Edition:

Date         Time   Version       Size       Filename     Folder
-----------------------------------------------------------------
24-Mar-2004  01:02  5.2.3790.136  1,642,496  Gdiplus.dll  
24-Mar-2004  01:02  5.2.3790.121    751,104  Sxs.dll      RTMQFE

Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:

Date         Time   Version         Size       Filename         Platform  Folder
--------------------------------------------------------------------------------
24-Mar-2004  01:02  5.2.3790.136    4,719,104  Gdiplus.dll      IA-64
24-Mar-2004  01:02  5.2.3790.136    1,642,496  Gdiplus.dll      x86
24-Mar-2004  01:02  5.2.3790.121    1,860,608  Sxs.dll          IA-64     RTMQFE
24-Mar-2004  01:02  5.2.3790.121      751,104  Wsxs.dll         x86       RTMQFE\WOW

Verifying Update Installation

•	Microsoft Baseline Security Analyzer (MBSA) 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 documented in the appropriate file information table. Note Attributes other than 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•	Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB833987\Filelist 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 833987 security update into the Windows installation source files.

Top of section

Note For Windows XP 64-Bit Edition Version 2003, this security update is the same as the Windows Server 2003 64-Bit Edition security update.

Prerequisites
This security update requires the release version of Windows XP or Windows XP Service Pack 1 (SP1). For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs:
The update for this issue is included in Windows XP Service Pack 2.

Installation Information

This security update supports the following setup switches:

      /help                 Displays the command line options

Setup Modes

      /quiet              Quiet mode (no user interaction or display)

      /passive            Unattended mode (progress bar only)

      /uninstall          Uninstalls the package

Restart Options

      /norestart          Do not restart when installation is complete

      /forcerestart      Restart after installation

Special Options

      /l           Lists installed Windows hotfixes or update packages

      /o          Overwrite OEM files without prompting

      /n          Do not backup files needed for uninstall

      /f           Force other programs to close when the computer shuts down

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Deployment Information

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

Windowsxp-kb833987-x86-enu /passive /quiet

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

Windowsxp-kb833987-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

In some cases, this update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe is located in the %Windir%\$NTUninstallKB833987$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

   /?: Show the list of installation switches.

   /u: Use unattended mode.

   /f: Force other programs to quit when the computer shuts down.

   /z: Do not restart when the installation is complete.

   /q: Use Quiet mode (no user interaction).

File Information

The English version of this update 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.

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

Date         Time   Version        Size       File name     Folder
--------------------------------------------------------------------------
09-Mar-2004  01:58  5.1.2600.136     646,656  Sxs.dll       SP1 (Pre SP1)
02-Mar-2004  21:19  5.1.3102.1360  1,638,400  Gdiplus.dll   SP1 (Pre SP1)
09-Mar-2004  02:25  5.1.2600.1363    676,864  Sxs.dll       SP2 (With SP1)
02-Mar-2004  21:19  5.1.3102.1360  1,638,400  Gdiplus.dll   SP2 (With SP1)

Windows XP 64-Bit Edition Service Pack 1:

Date         Time   Version        Size       File name        Platform
--------------------------------------------------------------------------
09-Mar-2004  02:33  5.1.2600.1363  2,018,816  Sxs.dll          IA-64
09-Mar-2004  02:25  5.1.2600.1363    676,864  Wsxs.dll         x86
09-Mar-2004  02:33  5.1.3102.1360  5,185,536  Gdiplus.dll      IA-64

Windows XP 64-Bit Edition Version 2003:

Date         Time   Version         Size       File name        Platform  Folder
   --------------------------------------------------------------------------------
24-Mar-2004  01:02  5.2.3790.136    4,719,104  Gdiplus.dll      IA-64
24-Mar-2004  01:02  5.2.3790.136    1,642,496  Gdiplus.dll      x86
24-Mar-2004  01:02  5.2.3790.121    1,860,608  Sxs.dll          IA-64     RTMQFE
24-Mar-2004  01:02  5.2.3790.121      751,104  Wsxs.dll         x86    RTMQFE\WOW

Notes

The Windows XP, Windows XP Service Pack 1, and Windows XP 64-Bit Edition Version 2003 versions of this security update are packaged as dual-mode packages, which contain files for both the original version of Windows XP and Windows XP Service Pack 1. For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.

Verifying Update Installation

•	Microsoft Baseline Security Analyzer (MBSA) 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 documented in the appropriate file information table. Note Attributes other than 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•	Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry keys. For Windows XP Home Edition, Windows XP Professional, Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP 64-Bit Edition Service Pack 1, Windows XP Tablet PC Edition, and Windows XP Media Center Edition: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB833987\Filelist For Windows XP 64-Bit Edition Version 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB833987\Filelist Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 833987 security update into the Windows installation source files.

Top of section

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 later. 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 in order to install the client security update. Before you install this update, install Office XP SP3. For additional information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671. The administrative update can also be installed on systems that are running Office XP Service Pack 2 or Office XP Service Pack 3. The security update for Office XP Service Pack 2 is only provided as part of the Office XP administrative security update.

For additional information about how to determine the version of Office XP on your computer, see Microsoft Knowledge Base Article 291331.

Note The administrative version of this update includes the necessary files to support installation on localized versions of the affected product, although the security update installation user interface will be in English.

Inclusion in Future Service Packs:

The fix for this issue will be included in a future service pack.

Restart Requirement

No restart is required.

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

Microsoft recommends that you install the Microsoft Office XP 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 required 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 Start Installation 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:

   /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: <full 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: <Cmd> Override Install Command defined by author. Specifies the path and name of the setup .inf or .exe file.

   /R:N Never restarts the computer after installation.

   /R:I Prompts the user to restart the computer if a restart is required, except when used with /Q:A.

   /R:A Always restarts the computer after installation.

   /R:S Restarts the computer after installation without prompting the user.

   /N:V No version checking - Install the program over any previous version.

Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to 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 indicates 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 (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.

Office XP:

Date         Time   Version      Size       Filename
--------------------------------------------------------
07-May-2004  21:56  10.0.6714.0  9,796,288  Mso.dll

Verifying Update Installation

•

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 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 the update installation. 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 the manner in which the files are extracted from within the security update:

   /? Displays the command line options

   /Q Specifies quiet mode, or suppresses prompts, when files are being extracted.

   /T: <full 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: <Cmd> Override 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 please perform the following procedure:

1.	Download the administrative 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.	In the Type the location where you want to place the extracted files box, type c:\adminUpdate, and then click OK.
8.	Click Yes when you are prompted to create the folder.
9.	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, 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.
10.	Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
11.	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, Data1.msi), and Feature List is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL.

Note Additional instructions are provided in Microsoft Knowledge Base Article 832332. Information concerning this update can also be found on the Microsoft Office XP Resource Kit Web site. General information concerning the Microsoft Office XP Resource Kit can also be found on TechNet. 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 (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.

Office XP:

Date         Time   Version      Size       Filename
   --------------------------------------------------------
07-May-2004  21:56  10.0.6714.0  9,796,288  Mso.dll

Verifying Update Installation

•

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 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 the update installation. 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