Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS08-044 - Critical

Vulnerabilities in Microsoft Office Filters Could Allow Remote Code Execution (924090)

Published: August 12, 2008 | Updated: August 13, 2008

Version: 1.1

General Information

Executive Summary

This security update resolves five privately reported vulnerabilities. These vulnerabilities could allow remote code execution if a user viewed a specially crafted image file using Microsoft Office. 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.

This security update is rated Critical for supported editions of Microsoft Office 2000, and Important for supported editions of Microsoft Office XP, Microsoft Office 2003 Service Pack 2, Microsoft Project 2002 Service Pack 1, Microsoft Office Converter Pack, and Microsoft Works 8. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by modifying the way that Microsoft Office parses the length of a file before passing the file to the allocated buffer. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. None

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Office Suite and Other SoftwareMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Office Suites and Components
Microsoft Office 2000 Service Pack 3
(KB921595)
Remote Code ExecutionCritical MS06-039
Microsoft Office XP Service Pack 3
(KB921596)
Remote Code ExecutionImportant MS06-039
Microsoft Office 2003 Service Pack 2
(KB921598)
Remote Code ExecutionImportant MS06-039
Other Office Software
Microsoft Office Project 2002 Service Pack 1
(KB921596)*
Remote Code ExecutionImportant MS06-039
Microsoft Office Converter Pack
(KB925256)
Remote Code ExecutionImportantNone
Microsoft Works 8
(KB955428)
Remote Code ExecutionImportantNone

*The update for this affected software is the same as the update for Microsoft Office XP Service Pack 3.

Non-Affected Software

Office and Other Software
Microsoft Visio 2002
Microsoft Visio 2003
Microsoft Office 2003 Service Pack 3
Microsoft Project Server 2003 Service Pack 3
2007 Microsoft Office System and 2007 Microsoft Office System Service Pack 1
Microsoft Project Server 2007
Microsoft Office Viewer 2003 and Microsoft Office Viewer 2003 Service Pack 3 for Excel, PowerPoint, Word, and Visio
Microsoft Office Viewer 2007 and Microsoft Office Viewer 2007 Service Pack 1 for Excel, PowerPoint, Word, and Visio
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1
Microsoft Office InfoPath 2003
Microsoft Office InfoPath 2007
Microsoft Office OneNote 2003
Microsoft Office OneNote 2007
Microsoft Works 9.0
Microsoft Works Suite 2005
Microsoft Works Suite 2006
Microsoft Office 2004 for Mac
Microsoft Office 2008 for Mac

Why was this bulletin revised on August 13, 2008? 
Microsoft revised this bulletin to clarify that the update for Microsoft Office Project 2002 Service Pack 1 is the same as the update for Microsoft Office XP Service Pack 3 in the Affected Software table. Because the update is the same, Project 2002 does not have a separate subsection in the section, Security Update Deployment. This is a bulletin change only. Customers who have already successfully installed this update do not have to reinstall.

I do not have all of the affected software installed, but I do have other Microsoft Office applications installed. Why am I being offered the security update? 
The vulnerabilities described in this security update exist within Microsoft Office but could not be exploited using one of the applications listed in the Non-Affected Software table. The Microsoft Office applications listed in the Non-Affected Software table use some of the same files as the applications listed in the Affected Software table to which the security update applies. We recommend installing the update to prevent the security update from being offered again.

I use Microsoft Office 2003 Service Pack 2. Are any additional security features included in this update? 
Yes, as part of the servicing model for Microsoft Office 2003, when users of Microsoft Office 2003 Service Pack 2 install this update, their systems will be upgraded to security functionality that was initially released with Microsoft Office 2003 Service Pack 3. All updates released after January 1, 2008 for Microsoft Office 2003 Service Pack 2 will include these security features, which were introduced in Microsoft Office 2003 Service Pack 3. We have thoroughly tested this update, but as with all updates, we recommend that users perform testing appropriate to the environment and configuration of their systems. For more information on this issue, please see Microsoft Knowledge Base Article 951646.

Where are the file information details? 
The file information details can be found in Microsoft Knowledge Base Article 924090.

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

I am using an older release of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

I use Microsoft Office 2003 Service Pack 3. Why am I still being offered this update? 
Microsoft Office 2003 Service Pack 3 is not impacted by the security vulnerabilities documented in this bulletin. However, users will still be offered this update because the files included with the update have a higher version number than the files that are currently on your system.

Does the offer to update a non-vulnerable version of Microsoft Office constitute an issue in the Microsoft update mechanism? 
No, the update mechanism is functioning correctly in that it detects a lower version of the files on the system than in the update package and thus, offers the update.

What is included in the Microsoft Office update that causes the higher version of the update files? 
The update files include changes to support stability changes in Microsoft Office and additional changes to support corporate environment changes. We have thoroughly tested this update, but as with all updates, we recommend that users perform testing appropriate to their environment and configurations of their systems.

Vulnerability Information

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareMicrosoft Malformed EPS Filter Vulnerability – CVE-2008-3019Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020Microsoft Office WPG Image File Heap Corruption Vulnerability - CVE-2008-3460Aggregate Severity Rating
Microsoft Office 2000 Service Pack 3 Critical
Remote Code Execution
Critical
Remote Code Execution
Critical
Remote Code Execution
Critical
Remote Code Execution
Critical
Remote Code Execution
Critical
Microsoft Office XP Service Pack 3 Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Microsoft Office 2003 Service Pack 2 Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Not applicable Important
Remote Code Execution
Important
Microsoft Office Project 2002 Service Pack 1 Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Microsoft Office Converter Pack Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Microsoft Works 8 Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important
Remote Code Execution
Important

A remote code execution vulnerability exists in the way that a Microsoft Office filter handles a malformed graphics image. An attacker could exploit the vulnerability by constructing a specially crafted Encapsulated PostScript (EPS) file that could allow remote code execution if a user opened the file with a Microsoft Office application. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3019.

Mitigating Factors for Microsoft Malformed EPS Filter Vulnerability - CVE-2008-3019

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file containing a specially crafted EPS image that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The vulnerability could be exploited by an attacker who convinced a user to open a specially crafted file. There is no way for an attacker to force a user to open a specially crafted file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message in order for this vulnerability to be exploited.
  • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Malformed EPS Filter Vulnerability - CVE-2008-3019

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Modify the Access Control List to deny access to EPSIMP32.FLT for all users

    Registry Method

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\EPS
    3. Take note of the value of Path. In explorer, navigate to the EPSIMP32.FLT file at the location listed as the value of Path.
    4. Right click on EPSIMP32.FLT file and select Properties.
    5. On the Security tab, click Advanced.
    6. Uncheck Allow inheritable permissions from the parent to propagate to this object… and click Remove.
    7. Click OK, Yes, and OK.

    Script Method

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /E /P everyone:N

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /E /P everyone:N

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT"

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /save %TEMP%\ EPSIMP32 _ACL.TXT

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /deny everyone:(F)

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT"

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /save %TEMP%\ EPSIMP32 _ACL.TXT

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /deny everyone:(F)

    Impact of Workaround. Office applications will not be able to import EPS images in Office documents.

    How to undo the workaround:

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /E /R everyone

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\EPSIMP32.FLT" /E /R everyone

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\EPSIMP32_ACL.TXT

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\EPSIMP32_ACL.TXT

  • Do not open or save documents that you receive from un-trusted sources or that you received unexpectedly from trusted sources.

FAQ for Microsoft Malformed EPS Filter Vulnerability - CVE-2008-3019

What is the scope of the vulnerability? 
A remote code execution vulnerability exists in Microsoft Office and could be exploited when a user opens a file containing a malformed graphics image or when a user inserts a malformed graphics image into an Office file. Such a file might also be included in an e-mail attachment. An attacker could exploit the vulnerability by constructing a specially crafted EPS file that could allow remote code execution.

If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability? 
When Microsoft Office opens a specially crafted EPS image file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability? 
This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in a Microsoft Office application.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted file to the user and by persuading the user to open the file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message sent to them in order for this vulnerability to be exploited.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers that have Microsoft Office installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
This update removes the vulnerability by modifying the way that Microsoft Office parses the length of an EPS file before passing the file 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.

A remote code execution vulnerability exists in the way that Microsoft Office handles a PICT-format image file. The vulnerability could be exploited when a Microsoft Office application opens a specially crafted PICT-format image file. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3018.

Mitigating Factors for Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file containing a specially crafted PICT image that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The vulnerability could be exploited by an attacker who convinced a user to open a specially crafted file. There is no way for an attacker to force a user to open a specially crafted file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message in order for this vulnerability to be exploited.
  • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Modify the Access Control List to deny access to PICTIM32.FLT for all users

    Registry Method

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\PICT
    3. Take note of the value of Path. In explorer, navigate to the PICTIM32.FLT file at the location listed as the value of Path.
    4. Right click on PICTIM32.FLT file and select Properties.
    5. On the Security tab, click Advanced.
    6. Uncheck Allow inheritable permissions from the parent to propagate to this object… and click Remove.
    7. Click OK, Yes, and OK.

    Script Method

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /P everyone:N

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /P everyone:N

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT"

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /save %TEMP%\ PICTIM32 _ACL.TXT

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /deny everyone:(F)

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT"

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /save %TEMP%\ PICTIM32 _ACL.TXT

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /deny everyone:(F)

    Impact of workaround: Users will not be able to import PICT format image files into Microsoft Office documents. This does not affect the rendering of already imported images embedded in Microsoft Office documents.

    How to undo the workaround:

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /R everyone

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /R everyone

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\PICTIM32_ACL.TXT

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\PICTIM32_ACL.TXT

  • Do not open or save documents that you receive from un-trusted sources or that you received unexpectedly from trusted sources.

FAQ for Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018

What is the scope of the vulnerability? 
A remote code execution vulnerability exists in Microsoft Office and could be exploited when a specially crafted PICT-format image file is opened by any of the affected Microsoft Office applications. Such a file might be included in an e-mail attachment or hosted on a malicious Web site. Viewing or previewing the specially crafted PICT-format image file in Outlook could not lead to exploitation of this vulnerability. An attacker could exploit this vulnerability only by constructing a specially crafted image file and convincing a user to open the file with one of the affected Office applications.

If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability? 
When Microsoft Office opens a specially crafted PICT image file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability? 
This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains a PICT-format image file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message sent to them in order for this vulnerability to be exploited.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers that have Microsoft Office installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
This update removes the vulnerability by modifying the way that Microsoft Office parses the length of a PICT-format image file before it passes the file 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.

A remote code execution vulnerability exists in the way that Microsoft Office handles a PICT-format image file. The vulnerability could be exploited when either a Microsoft Office application opens a specially crafted PICT-format image file. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3021.

Mitigating Factors for Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file containing a specially crafted PICT image that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The vulnerability could be exploited by an attacker who convinced a user to open a specially crafted file. There is no way for an attacker to force a user to open a specially crafted file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message in order for this vulnerability to be exploited.
  • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Modify the Access Control List to deny access to PICTIM32.FLT for all users

    Registry Method

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\PICT
    3. Take note of the value of Path. In explorer, navigate to the PICTIM32.FLT file at the location listed as the value of Path.
    4. Right click on PICTIM32.FLT file and select Properties.
    5. On the Security tab, click Advanced.
    6. Uncheck Allow inheritable permissions from the parent to propagate to this object… and click Remove.
    7. Click OK, Yes, and OK.

    Script Method

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /P everyone:N

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /P everyone:N

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT"

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /save %TEMP%\ PICTIM32 _ACL.TXT

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /deny everyone:(F)

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT"

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /save %TEMP%\ PICTIM32 _ACL.TXT

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /deny everyone:(F)

    Impact of workaround: Users will not be able to import PICT format image files into Microsoft Office documents. This does not affect the rendering of already imported images embedded in Microsoft Office documents.

    How to undo the workaround:

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /R everyone

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\PICTIM32.FLT" /E /R everyone

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\PICTIM32_ACL.TXT

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\PICTIM32_ACL.TXT

  • Do not open or save documents that you receive from un-trusted sources or that you received unexpectedly from trusted sources.

FAQ for Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021

What is the scope of the vulnerability? 
A remote code execution vulnerability exists in Microsoft Office and could be exploited when a specially crafted PICT-format image file is opened by any of the affected Microsoft Office applications. Such a file might be included in an e-mail attachment or hosted on a malicious Web site. Viewing or previewing the specially crafted PICT-format image file in Outlook could not lead to exploitation of this vulnerability. An attacker could exploit this vulnerability only by constructing a specially crafted image file and convincing a user to open the file with one of the affected applications.

If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability? 
When Microsoft Office opens a specially crafted PICT image file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability? 
This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message sent to them in order for this vulnerability to be exploited.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers that have Microsoft Office installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
This update removes the vulnerability by modifying the way that Microsoft Office parses the length of a PICT-format image file before passing the file 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.

A remote code execution vulnerability exists in the way that Microsoft Office handles a BMP format image file. The vulnerability could be exploited when a Microsoft Office application opens a specially crafted BMP-format image file. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3020.

Mitigating Factors for Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file containing a specially crafted BMP image that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The vulnerability could be exploited by an attacker who convinced a user to open a specially crafted file. There is no way for an attacker to force a user to open a specially crafted file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message in order for this vulnerability to be exploited.
  • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Modify the Access Control List to deny access to BMP32.FLT for all users

    Registry Method

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    For all supported editions of Microsoft Windows 2000

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\BMP
    3. Click Security, and then click Permissions.
    4. .Make a note of the permissions that are listed in this dialog box so that you can restore them to their original values at a later time.
    5. Uncheck Allow inheritable permissions from the parent to propagate to this object… and click Remove and OK.
    6. .A dialog warns that no one will be able to access this registry key with the current settings. Click Yes when prompted.

    For all supported editions of Windows XP Service Pack 1 or later operating systems

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\BMP
    3. Click Edit, and then click Permissions.
    4. Make a note of the permissions that are listed in this dialog box so that you can restore them to their original values at a later time.
    5. Click Advanced.
    6. Uncheck Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here. Click Remove, and then OK.
    7. A dialog warns that no one will be able to access this registry key with the current settings. Click Yes, and then click OK to close the Permissions for BMP dialog box.

    Impact of Workaround. Users will not be able to import BMP format image files into Microsoft Office documents. This does not affect the rendering of already imported images embedded in Microsoft Office documents.

    How to undo the workaround:
    Restore the previously configured permissions on the registry key.

    Script Method

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /E /P everyone:N

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /E /P everyone:N

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT"

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /save %TEMP%\BMP IMP32 _ACL.TXT

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /deny everyone:(F)

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT"

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /save %TEMP%\BMP IMP32 _ACL.TXT

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /deny everyone:(F)

    Impact of Workaround. Users will not be able to import BMP format image files into Microsoft Office documents. This does not affect the rendering of already imported images embedded in Microsoft Office documents.

    How to undo the workaround:

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /E /R everyone

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\BMPIMP32.FLT" /E /R everyone

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\BMPIMP32_ACL.TXT

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\BMPIMP32_ACL.TXT

  • Do not open or save documents that you receive from un-trusted sources or that you received unexpectedly from trusted sources.

FAQ for Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020

What is the scope of the vulnerability? 
A remote code execution vulnerability exists in Microsoft Office and could be exploited when a specially crafted BMP-format image file is opened by a Microsoft Office application. Such a file might be included in an e-mail attachment or hosted on a malicious Web site. Viewing or previewing the specially crafted BMP-format image file in Outlook could not lead to exploitation of this vulnerability. An attacker could exploit this vulnerability only by constructing a specially crafted image file and convincing a user to open the file with one of the affected applications.

If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability? 
When Microsoft Office opens a specially crafted BMP image file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability? 
This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in a Microsoft application.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message sent to them in order for this vulnerability to be exploited.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers that have Microsoft Office installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
This update removes the vulnerability by modifying the way that Microsoft Office parses the length of a BMP image file before passing the file 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.

A remote code execution vulnerability exists in the way that Microsoft Office handles a WordPerfect Graphics (WPG) format image file. The vulnerability could be exploited when Microsoft Office opens a specially crafted WPG-format image file or a WordPerfect document file with a malformed WPG image embedded. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-3460.

Mitigating Factors for Microsoft Office WPG Image File Heap Corruption Vulnerability - CVE-2008-3460

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file containing a specially crafted WPG image that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in an affected Microsoft Office application.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The vulnerability could be exploited by an attacker who convinced a user to open a specially crafted file. There is no way for an attacker to force a user to open a specially crafted file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message in order for this vulnerability to be exploited.
  • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Office WPG Image File Heap Corruption Vulnerability - CVE-2008-3460

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Modify the Access Control List to deny access to WPGIMP32.FLT for all users

    Registry Method

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    1. Click Start, click Run, type regedit.exe, and then click OK.
    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Graphics Filters\Import\WPG.
    3. Take note of the value of Path. In explorer, navigate to the WPGIMP32.FLT file at the location listed as the value of Path.
    4. Right click on WPGIMP32.FLT file and select Properties.
    5. On the Security tab, click Advanced.
    6. Uncheck Allow inheritable permissions from the parent to propagate to this object… and click Remove.
    7. Click OK, Yes, and OK.

    Script Method

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /E /P everyone:N

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /E /P everyone:N

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT"

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /save %TEMP%\WPG IMP32 _ACL.TXT

    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /deny everyone:(F)

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following commands from a command prompt as an administrator:
    takeown /f "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT"

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /save %TEMP%\WPG IMP32 _ACL.TXT

    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /deny everyone:(F)

    Impact of Workaround. Users will not be able to import WPG format image files into Microsoft Office documents. This does not affect the rendering of already imported images embedded in Microsoft Office documents.

    How to undo the workaround:

    For all supported 32-bit editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /E /R everyone

    For all supported x64-based editions of Windows XP
    Run the following command from a command prompt:
    cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT\WPGIMP32.FLT" /E /R everyone

    For all supported 32-bit editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\WPGIMP32_ACL.TXT

    For all supported x64-based editions of Windows Vista and Windows Server 2008
    Run the following command from a command prompt as an administrator:
    icacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\GRPHFLT" /restore %TEMP%\WPGIMP32_ACL.TXT

  • Do not open or save documents that you receive from un-trusted sources or that you received unexpectedly from trusted sources.

FAQ for Microsoft Office WPG Image File Heap Corruption Vulnerability - CVE-2008-3460

What is the scope of the vulnerability? 
A remote code execution vulnerability exists in Microsoft Office and could be exploited when a specially crafted WPG image file or a specially crafted WordPerfect document file is opened by a Microsoft Office application. Such a file might be included in an e-mail attachment or hosted on a malicious Web site. Viewing or previewing the specially crafted WPG image file in Outlook could not lead to exploitation of this vulnerability. An attacker could exploit this vulnerability only by constructing a specially crafted image file and convincing a user to open the file with one of the affected applications.

If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability? 
When Microsoft Office opens a specially crafted WPG image file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability? 
This vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince the user to open the file in a Microsoft application.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. Additionally, when Microsoft Word is being used as the HTML e-mail editor in Outlook, a user would need to reply to or forward a malicious e-mail message sent to them in order for this vulnerability to be exploited.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers that have Microsoft Office installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
This update removes the vulnerability by modifying the way that Microsoft Office parses the length of a WPG image file before passing the file 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.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA 2.1
Microsoft Office 2000 Service Pack 3No
Microsoft Office XP Service Pack 3Yes
Microsoft Office 2003 Service Pack 2Yes
Microsoft Office Converter PackYes
Microsoft Works 8Yes*

*Note If the system uses Microsoft Update for update scanning and can access Microsoft Update (which a scan report can determine), MBSA 2.1 will detect Microsoft Works 8. However, if the system is managed by WSUS or is in an offline secure environment, which forces the system to use the WSUSSCN2.CAB offline catalog, MBSA 2.1 will not detect Microsoft Works 8.

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Note For customers using legacy software not supported by MBSA 2.1, Microsoft Update, and Windows Server Update Services: please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can 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. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

SoftwareSMS 2.0SMS 2003 with SUSFPSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Office 2000 Service Pack 3YesYesNoNo
Microsoft Office XP Service Pack 3YesYesYesYes
Microsoft Office 2003 Service Pack 2YesYesYesYes
Microsoft Office Converter PackYesYesYesYes
Microsoft Works 8NoNoNoNo

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Note If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.

Office Administrative Installation Point

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

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Affected Software

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

Office 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionOffice2000-KB921595-FullFile-enu /q:a
Installing without restartingOffice2000-KB921595-FullFile-enu /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the subsection, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features subsection in this section.

Restart Requirement
Restart requiredThis update does not require a restart.
HotpatchingNot applicable
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 media.
File Information See Microsoft Knowledge Base Article 921595
Registry Key Verification Not applicable

Office Features for Administrative Installations

Server administrators who use a Windows Installer Administrative Installation must update the server location. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

The following table contains 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
MSPUB, O9PUB, 09PBProductFiles,PubPrimary,MSDrawFiles
O9EXLProductFiles, EXCELNonBootFiles
O9PRMProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, FPClientNonBootFiles, PPTNonBootFiles, ProductNonBootFiles
O9PROProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, PPTNonBootFiles
O9SBE, 9327_o9procd1_sbe_coxs_slv_data1 productProductFiles, OUTLOOKNonBootFiles,WORDNonBootFiles, EXCELNonBootFiles
O9FPProductFiles, FPClientNonBootFiles, ProductNonBootFiles
O9PIPC1ProductFiles, OUTLOOKNonBootFiles, MSDrawFiles, WORDNonBootFiles, EXCELNonBootFiles
O9PIPC2ProductFiles, MSDrawFiles, WORDNonBootFiles, EXCELNonBootFiles
O9PRMCD2ProductFiles,AccessRuntimeMaster, PubPrimary, MSDrawFiles, SBCMNonBootFiles
O9STDProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, EXCELNonBootFiles, PPTNonBootFiles

Note Administrators working in managed environments can find resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the setup switches supported by Windows Installer.

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

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.

Removing the Update

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

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. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several versions and editions of Microsoft Office, the following steps may be different on your system. 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 system 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.

Office XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionOfficeXP-KB921596-FullFile-enu /q:a
Installing without restartingOfficeXP-KB921596-FullFile-enu /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the subsection, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features subsection in this section.

Restart Requirement
Restart requiredThis update does not require a restart.
HotpatchingNot applicable
Removal Information Use 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.

File Information See Microsoft Knowledge Base Article 921596
Registry Key Verification Not applicable

Office Features

The following table contains 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
ACCESS, FP, OUTLOOK, PPT, ACCESSRT, PUBProductFiles
PIPC1, PROPLUS, PRO, SBE, STD, STDEDUProductFiles
EXCELEXCELNonBootFiles, ProductFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

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.

Removing the Update

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.

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. See the “Microsoft Baseline Security Analyzer” heading under the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. 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 system 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.

Office 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup.
Deployment
Installing without user interventionOffice2003-KB921598-FullFile-enu /q:a
Installing without restartingOffice2003-KB921598-FullFile-enu /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the subsection, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features subsection in this section.

Restart Requirement
Restart requiredThis update does not require a restart.
HotpatchingNot applicable
Removal Information Use 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.

File Information See Microsoft Knowledge Base Article 921598
Registry Key Verification Not applicable

Office Features

The following table contains 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
STD11, BASIC11, PERS11, STDP11WORDNonBootFiles, EXCELNonBootFiles, ProductFiles
FP11ProductFiles
PROI11, PRO11, PRO11SBWORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, ProductFiles
XLVIEWExcelViewer

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of 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.

Removing the Update

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.

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. See the “Microsoft Baseline Security Analyzer” heading under the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. 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 system 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.

Microsoft Office Converter Pack

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionOffice2003-KB925256-FullFile-enu /q:a
Installing without restartingOffice2003-KB925256-FullFile-enu /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the subsection, Microsoft Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features subsection in this section.

Restart Requirement
Restart requiredThis update does not require a restart.
HotpatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel.
File Information See Microsoft Knowledge Base Article 925256
Registry Key Verification Not applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your computer. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the system after installation.
/r:I Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a Always restarts the system after installation.
/r:s Restarts the system after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of 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.

Removing the Update

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

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

    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.

Microsoft Works 8

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user interventionKB955428_en-US /q:a
Installing without restartingKB955428_en-US /r:n
Update log fileNot applicable
Further informationFor detection and deployment, see the subsection, Microsoft Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features subsection in this section.

Restart Requirement
Restart requiredThis update does not require a restart.
HotpatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel.
File Information See Microsoft Knowledge Base Article 955428
Registry Key Verification Not applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your computer. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passive Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart Suppresses restarting the system if the update requires a restart.
/forcerestart Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract Extracts the files without installing them. You are prompted for a target folder.
/extract:<path> Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID> Forces the use of a specific language, when the update package supports that language.
/log:<log file> Enables logging, by both Vnox and Installer, during the update installation.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of 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.

Removing the Update

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

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

    Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

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

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

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

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Shaun Colley of NGS Software for reporting the Microsoft Malformed PICT Filter Vulnerability (CVE-2008-3018).
  • Damian Put working with the Zero Day Initiative (ZDI) for reporting the Microsoft PICT Filter Parsing Vulnerability (CVE-2008-3021).
  • An anonymous researcher working with the iDefense VCP for reporting the Microsoft Malformed BMP Filter Vulnerability (CVE-2008-3020).
  • Damian Put working with the iDefense VCP for reporting the Microsoft Office WPG Image File Heap Corruption Vulnerability (CVE-2008-3460).

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.

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 (August 12, 2008): Bulletin published.
  • V1.1 (August 13, 2008): Clarified that the update for Microsoft Office Project 2002 Service Pack 1 is the same as the update for Microsoft Office XP Service Pack 3. Customers who have already successfully installed this update do not have to reinstall.

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

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.