Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Office / Word / Excel / Power Point multiple security vulnerabilities

  iDefense Security Advisory 08.12.08: Microsoft Excel FORMAT Record Invalid Array Index Vulnerability

  iDefense Security Advisory 08.12.08: Microsoft Excel Chart AxesSet Invalid Array Index Vulnerability

  iDefense Security Advisory 08.12.08: Microsoft PowerPoint Viewer 2003 Cstring Integer Overflow Vulnerability

  iDefense Security Advisory 08.12.08: Microsoft PowerPoint Viewer 2003 Out of Bounds Array Index Vulnerability

From:MICROSOFT <secure_(at)_microsoft.com>
Date:12.08.2008
Subject:Microsoft Security Bulletin MS08-044 – Critical Vulnerabilities in Microsoft Office Filters Could Allow Remote Code Execution (924090)

Microsoft Security Bulletin MS08-044 – Critical
Vulnerabilities in Microsoft Office Filters Could Allow Remote Code Execution (924090)
Published: August 12, 2008

Version: 1.0
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
Top of sectionTop of section
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 Software Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Office Suites and Components

Microsoft Office 2000 Service Pack 3
(KB921595)


Remote Code Execution


Critical


MS06-039

Microsoft Office XP Service Pack 3
(KB921596)


Remote Code Execution


Important


MS06-039

Microsoft Office 2003 Service Pack 2
(KB921598)


Remote Code Execution


Important


MS06-039
Other Office Software

Microsoft Office Project 2002 Service Pack 1
(KB921596)


Remote Code Execution


Important


MS06-039

Microsoft Office Converter Pack
(KB925256)


Remote Code Execution


Important


None

Microsoft Works 8
(KB955428)


Remote Code Execution


Important


None

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
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

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.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Microsoft Malformed EPS Filter Vulnerability – CVE-2008-3019 Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018 Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021 Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020 Microsoft Office WPG Image File Heap Corruption Vulnerability - CVE-2008-3460 Aggregate 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 36)


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 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
Top of sectionTop of section

Microsoft Malformed EPS Filter Vulnerability - CVE-2008-3019

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.
Top of sectionTop of section

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.
Top of sectionTop of section

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.
Top of sectionTop of section
Top of sectionTop of section

Microsoft Malformed PICT Filter Vulnerability - CVE-2008-3018

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.
Top of sectionTop of section

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.
Top of sectionTop of section

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.
Top of sectionTop of section
Top of sectionTop of section

Microsoft PICT Filter Parsing Vulnerability - CVE-2008-3021

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.
Top of sectionTop of section

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.
Top of sectionTop of section

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.
Top of sectionTop of section
Top of sectionTop of section

Microsoft Malformed BMP Filter Vulnerability - CVE-2008-3020

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.
Top of sectionTop of section

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.
Top of sectionTop of section

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.
Top of sectionTop of section
Top of sectionTop of section

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

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.
Top of sectionTop of section

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.
Top of sectionTop of section

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.

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.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod