Lucene search

SecurityvulnsSECURITYVULNS:DOC:20970

HistoryDec 10, 2008 - 12:00 a.m.

Microsoft Security Bulletin MS08-072 - Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)

2008-12-1000:00:00

vulners.com

Microsoft Security Bulletin MS08-072 - Critical
Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)
Published: December 9, 2008

Version: 1.0
General Information
Executive Summary

This security update resolves eight privately reported vulnerabilities in Microsoft Office Word and Microsoft Office Outlook that could allow remote code execution if a user opens a specially crafted Word or Rich Text Format (RTF) file. An attacker who successfully exploited these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for supported editions of Microsoft Office Word 2000 and Microsoft Office Outlook 2007. For supported editions of Microsoft Office Word 2002, Microsoft Office Word 2003, Microsoft Office Word 2007, Microsoft Office Compatibility Pack, Microsoft Office Word Viewer 2003, Microsoft Works 8, Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac, this security update is rated Important. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by modifying the way that Microsoft Office Word and Microsoft Office Outlook handle specially crafted Word and Rich Text Format (RTF) files. For more information about the vulnerability, 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. Microsoft Knowledge Base Article 957173 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
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 Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Office Suites and Components

Microsoft Office 2000 Service Pack 3

Microsoft Office Word 2000 Service Pack 3
(KB956328)

Remote Code Execution

Critical

MS08-026

Microsoft Office XP Service Pack 3

Microsoft Office Word 2002 Service Pack 3
(KB956329)

Remote Code Execution

Important

MS08-042

Microsoft Office 2003 Service Pack 3

Microsoft Office Word 2003 Service Pack 3
(KB956357)

Remote Code Execution

Important

MS08-042

2007 Microsoft Office System

Microsoft Office Word 2007
(KB956358)

Remote Code Execution

Important

MS08-026

2007 Microsoft Office System

Microsoft Office Outlook 2007
(KB956358)

Remote Code Execution

Critical

None

2007 Microsoft Office System Service Pack 1

Microsoft Office Word 2007 Service Pack 1
(KB956358)

Remote Code Execution

Important

MS08-026

2007 Microsoft Office System Service Pack 1

Microsoft Office Outlook 2007 Service Pack 1
(KB956358)

Remote Code Execution

Critical

None
Other Office Software

Microsoft Office Word Viewer 2003
(KB956366)

Not applicable

Remote Code Execution

Important

MS08-026

Microsoft Office Word Viewer 2003 Service Pack 3
(KB956366)

Not applicable

Remote Code Execution

Important

MS08-026

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
(KB956828)

Not applicable

Remote Code Execution

Important

MS08-026

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1
(KB956828)

Not applicable

Remote Code Execution

Important

MS08-026

Microsoft Works 8*
(KB959487)

Not applicable

Remote Code Execution

Important

MS08-052
Microsoft Office for Mac

Microsoft Office 2004 for Mac
(KB960402)

Not applicable

Remote Code Execution

Important

MS08-057

Microsoft Office 2008 for Mac
(KB960401)

Not applicable

Remote Code Execution

Important

MS08-057

Open XML File Format Converter for Mac
(KB960403)

Not applicable

Remote Code Execution

Important

MS08-057

*In order to be offered this security update, customers running Microsoft Works 8.0 must first update to Works 8.5 as described in Microsoft Works Update. This includes all customers using Microsoft Works 8.0, Works Suite 2004, and Works Suite 2005. For customers running Works Suite 2006, Works 8.5 is already included.

Non-Affected Software
Office and Other Software Component

Microsoft Office 2000 Service Pack 3

Microsoft Office Outlook 2000 Service Pack 3

Microsoft Office XP Service Pack 3

Microsoft Office Outlook 2002 Service Pack 3

Microsoft Office 2003 Service Pack 3

Microsoft Office Outlook 2003 Service Pack 3

Microsoft Works 9.0

Not applicable
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

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

MS08-074 also describes vulnerabilities in Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac. How does MS08-074 relate to this bulletin (MS08-072)?
This security update for Microsoft Office 2004 for Mac (960402), Microsoft Office 2008 for Mac (960401), and Open XML File Format Converter for Mac (960403) also addresses the vulnerabilities described in MS08-074. Users with Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, or Open XML File Format Converter for Mac installed will have to install this security update but will only need to install it once.

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.

Why is this update rated Critical for Outlook 2007?
Outlook 2007 default configuration uses Microsoft Office Word 2007 as the default e-mail editor. When using Microsoft Office Word as the default e-mail editor on Microsoft Office Outlook 2007, this vulnerability can be exploited using the preview pane requiring no user interaction. As a result Microsoft Office Outlook 2007 has been rated critical.

Why is this update Critical for Word 2000 but only Important for all other affected versions of Word?
Microsoft Office Word 2002 and later versions have a built-in feature that prompts a user to Open, Save, or Cancel before opening a document. This mitigating factor reduces the vulnerability from Critical to Important because the vulnerability requires more than a single user action to complete the exploit.

This is a Microsoft Office Word update. Why are Microsoft Office Outlook 2007 and Microsoft Office Outlook 2007 Service Pack 1 referenced in the Affected Software table?
The files that are updated to address the vulnerabilities documented in this bulletin are core files to Microsoft Office Word. For Microsoft Office Word 2007 and Microsoft Office Word 2007 Service Pack 1, some of these core files are shared with Microsoft Office Outlook 2007 and Microsoft Office Outlook 2007 Service Pack 1, and provide functionality, such as editing, to Outlook. Therefore, Outlook 2007 and Outlook 2007 Service Pack 1 need to be updated as well, and Word 2007 and Word 2007 Service Pack 1 and Outlook 2007 and Outlook 2007 Service Pack 1 are serviced by the same package.

Users with only Outlook 2007 or Outlook 2007 Service Pack 1 installed will still need to apply this Word update to their systems. Users with Outlook 2007 or Outlook 2007 Service Pack 1 that also have Word 2007 or Word 2007 Service Pack 1 installed will also need to apply this update but they will only need to install it once. For more information on this issue, please see Microsoft Knowledge Base Article 949370.

I am using Works 8.0, how do I update to Works 8.5?
Microsoft has provided a free update for Works 8.0 users to Works 8.5. As a result, all customers using Microsoft Works 8.0, Works Suite 2005, or Works Suite 2004 should update to the security-enhanced Works 8.5. Please see Microsoft Works Update for more information.

How do I know if I need to update my version of Works?
Find out whether you need an update by determining which Works version you have. Simply start the Works Task Launcher and click on the Help button. If the last option in the Help menu reads, "About Microsoft Works Suite 2004," then you are eligible to update. If the last option reads, "About Microsoft Works," then select that option. In the "About Microsoft Works" dialog, look for the version number. If the version is 8.0, then you are eligible to update. If it displays Works 8.5, then you already have the most current version of the software.

What components of the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats are updated by this bulletin?
The update included with this security bulletin applies only to the specific component within the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats that is affected. For example, in an Excel bulletin, only the Excel compatibility pack component files are included in the update packages and not Word or PowerPoint compatibility pack component files. Word compatibility pack component files are updated in a Word bulletin and PowerPoint compatibility pack component files are updated in a PowerPoint bulletin.

The Office component discussed in this article is part of the Office Suite that I have installed on my system; however, I did not choose to install this specific component. Will I be offered this update?
Yes, if the version of the Office Suite installed on your system shipped with the component discussed in this bulletin, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that shipped with the particular Office Suite and offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is included in the version of the Office Suite, will not increase the security risk of that system. However, users who do choose to install the update will not have a negative impact on the security or performance of a system. For more information on this issue, please see Microsoft Knowledge Base Article 830335.

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.

I use Microsoft Office 2007 RTM. Are any additional security features included in this update?
Yes, as part of the servicing model for Microsoft Office 2007, when users of Microsoft Office 2007 RTM install this update, their systems will be upgraded to functionality that was initially released with Microsoft Office 2007 Service Pack 1. All updates released after December 8, 2007 for Microsoft Office 2007 will include these security features, which were introduced in Microsoft Office 2007 Service Pack 1. 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.

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

Severity Ratings and Vulnerability Identifiers
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Word Memory Corruption Vulnerability - CVE-2008-4024 Word RTF Object Parsing Vulnerability - CVE-2008-4025 Word Memory Corruption Vulnerability - CVE-2008-4026 Word RTF Object Parsing Vulnerability - CVE-2008-4027 Word RTF Object Parsing Vulnerability - CVE-2008-4030 Word RTF Object Parsing Vulnerability - CVE-2008-4028 Word RTF Object Parsing Vulnerability - CVE-2008-4031 Word Memory Corruption Vulnerability - CVE-2008-4837 Aggregate Severity Rating
Office Software

Microsoft Office Word 2000 Service Pack 3

Critical
Remote Code Execution

Microsoft Office Word 2002 Service Pack 3

Important
Remote Code Execution

Microsoft Office Word 2003 Service Pack 3

None

Important
Remote Code Execution

Microsoft Office Word 2007

None

Important
Remote Code Execution

Outlook 2007

None

Critical
Remote Code Execution

None

Critical
Remote Code Execution

None

Critical
Remote Code Execution

Microsoft Office Word 2007 Service Pack 1

None

Important
Remote Code Execution

Outlook 2007 Service Pack 1

None

Critical
Remote Code Execution

None

Critical
Remote Code Execution

None

Critical
Remote Code Execution

Microsoft Office Word Viewer 2003

None

Important
Remote Code Execution

Microsoft Office Word Viewer 2003 Service Pack 3

None

Important
Remote Code Execution

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats

None

Important
Remote Code Execution

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1

None

Important
Remote Code Execution

Microsoft Works 8

None

Important
Remote Code Execution

Microsoft Office 2004 for Mac

Important
Remote Code Execution

None

Important
Remote Code Execution

None

Important
Remote Code Execution

Microsoft Office 2008 for Mac

None

Important
Remote Code Execution

None

Important
Remote Code Execution

None

Important
Remote Code Execution

Open XML File Format Converter for Mac

None

Important
Remote Code Execution

None

Important
Remote Code Execution

None

Important
Remote Code Execution
Top of sectionTop of section

Word Memory Corruption Vulnerability - CVE-2008-4024

A remote code execution vulnerability exists in the way that Word handles specially crafted Word files. The vulnerability could allow remote code execution if a user opens a specially crafted Word file with a malformed record. 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.

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

Mitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4024

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

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 cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
•

In a Web-based attack scenario, a Web site could contain a Word file that is used to exploit this vulnerability. An attacker would have to convince users to visit the Web site and open a specially crafted Word file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site, and then convincing them to open the specially crafted Word file.
•

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 Word Memory Corruption Vulnerability - CVE-2008-4024

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

Do not open or save Microsoft Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
Top of sectionTop of section

FAQ for Word Memory Corruption Vulnerability - CVE-2008-4024

What causes the vulnerability?
When a user opens a specially crafted Office 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 run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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.

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word file to the user and by convincing the user to open the file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Word is used, including workstations and terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word opens files. However, after applying this update, attempts to open a specially crafted Microsoft Word document may still cause Word to exit or return an error unexpectedly. This behavior is not exploitable.

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

Word RTF Object Parsing Vulnerability - CVE-2008-4025

A remote code execution vulnerability exists in the way that Microsoft Office handles specially crafted Rich Text Format (RTF) files. The vulnerability could allow remote code execution if a user opens a specially crafted RTF file in Word or reads a specially crafted e-mail sent in the RTF format. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4025

In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convincing them to open the specially crafted RTF file.
•

Workarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4025

Prevent Word from loading RTF files

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.

For Word 2003 Interactive

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

.On the File menu, click Exit to exit Registry Editor.

For Word 2003Managed Deployment Script

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

For Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

Impact of workaround. RTF files will not be readable by Word.

How to undo the workaround.

Rollback for Word 2003 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2003 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg

Rollback for Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg
•

Read e-mails in plain text

Read e-mail messages in plain text format if you are using Microsoft Office Outlook 2002 or a later version, or Outlook Express 6 SP1 or a later version, to help protect yourself from the RTF e-mail attack vector.

Microsoft Office Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Office Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.

Digitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.

For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
•

The changes are applied to the preview pane and to open messages.
•

Pictures become attachments so that they are not lost.
•

Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
Top of sectionTop of section

FAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4025

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
The vulnerability is caused by a memory calculation error when processing a malformed control word in a specially crafted RTF file. The error 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 control of an affected system in the context of the currently logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted RTF file with an affected version of Microsoft Office Word or read a specially crafted e-mail in Microsoft Office Outlook with Word as the default e-mail editor.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted RTF e-mail to a system that uses Word as its default editor. The vulnerability could be exploited when a user reads or previews the e-mail.

Note By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a RTF file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site, and then convincing them to open the specially crafted RTF file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Word or Microsoft Office Outlook is used are primarily at risk, including workstations and terminal servers. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.

Word Memory Corruption Vulnerability - CVE-2008-4026

A remote code execution vulnerability exists in the way that Word handles specially crafted Word files. The vulnerability could allow remote code execution if a user opens a specially crafted Word file with a malformed value. 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.

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

Mitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4026

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
•

In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site., and then convincing them to open the specially crafted Word file
Top of sectionTop of section

Workarounds for Word Memory Corruption Vulnerability - CVE-2008-4026

On Word client systems, use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or un-trusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:
Command to use to enable MOICE to be the registered handler Command to use to disable MOICE as the registered handler

ASSOC .doc=oice.word.document

ASSOC .doc=Word.Document.8

Note On Windows Vista and Windows Server 2008, the commands will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Impact of Workaround. Office 2003 and earlier formatted documents that are converted to the 2007 Microsoft Office System Open XML format by MOICE will not retain macro functionality. Additionally, documents with passwords or that are protected with Digital Rights Management cannot be converted.
Top of sectionTop of section

FAQ for Word Memory Corruption Vulnerability - CVE-2008-4026

What causes the vulnerability?
When a user opens a specially crafted Word 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 run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. 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.

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted Word file to the user and by convincing the user to open the file.

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

What systems are primarily at risk from the vulnerability?
Systems where the affected software is used, including workstations and terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

Word RTF Object Parsing Vulnerability - CVE-2008-4027

A remote code execution vulnerability exists in the way that Microsoft Office handles specially crafted Rich Text Format (RTF) files. The vulnerability could allow remote code execution if a user opens a specially crafted RTF file with malformed control words in Word, or views or previews a specially crafted RTF file with malformed control words in rich text e-mail. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4027

Workarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4027

Prevent Word from loading RTF files

For Word 2003 Interactive

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2003Managed Deployment Script

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

For Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

Impact of workaround. RTF files will not be readable by Word.

How to undo the workaround.

Rollback for Word 2003 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2003 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg

Rollback for Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg
•

Read e-mails in plain text

For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
•

The changes are applied to the preview pane and to open messages.
•

Pictures become attachments so that they are not lost.
•

Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
Top of sectionTop of section

FAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4027

What causes the vulnerability?
The vulnerability is caused by a memory calculation error when processing a specially crafted control word in a RTF file. The error may corrupt system memory in such a way that an attacker could execute arbitrary code. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system.

Note By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Word or Microsoft Office Outlook is used are primarily at risk, such as workstations and terminal servers. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way Word cleans up memory after encountering malformed RTF content.

Word RTF Object Parsing Vulnerability - CVE-2008-4030

A remote code execution vulnerability exists in the way that Microsoft Office handles specially crafted Rich Text Format (RTF) files. The vulnerability could allow remote code execution if a user opens a specially crafted RTF file in Word or reads or previews a specially crafted e-mail sent in the RTF format. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-in user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4030

Workarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4030

Prevent Word from loading RTF files

For Word 2003 Interactive

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2003Managed Deployment Script

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

For Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

Impact of workaround. RTF files will not be readable by Word.

How to undo the workaround.

Rollback for Word 2003 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2003 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg

Rollback for Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg
•

Read e-mails in plain text

For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
•

The changes are applied to the preview pane and to open messages.
•

Pictures become attachments so that they are not lost.
•

Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
Top of sectionTop of section

FAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4030

What causes the vulnerability?
The vulnerability is caused by a memory calculation error when processing a specially crafted control words in an RTF file. The error may corrupt system memory in such a way that an attacker could execute arbitrary code. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system.

Note By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.

What does the update do?
The update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.

Word RTF Object Parsing Vulnerability - CVE-2008-4028

A remote code execution vulnerability exists in the way that Microsoft Office handles specially crafted Rich Text Format (RTF) files. The vulnerability could allow remote code execution if a user opens a specially crafted RTF file in Word, or reads or previews a specially crafted e-mail sent in the RTF format. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-in user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4028

Workarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4028

Prevent Word from loading RTF files

For Word 2003 Interactive

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2003Managed Deployment Script

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

For Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

Impact of workaround. RTF files will not be readable by Word.

How to undo the workaround.

Rollback for Word 2003 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2003 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg

Rollback for Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg
•

Read e-mails in plain text

For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
•

The changes are applied to the preview pane and to open messages.
•

Pictures become attachments so that they are not lost.
•

Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
Top of sectionTop of section

FAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4028

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system.

Note By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.

What does the update do?
The update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.

Word RTF Object Parsing Vulnerability - CVE-2008-4031

A remote code execution vulnerability exists in the way that Microsoft Office handles specially crafted Rich Text Format (RTF) files. The vulnerability could allow remote code execution if a user opens a specially crafted RTF file in Word, or reads or previews a specially crafted e-mail sent in the RTF format. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4031

Workarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4031

Prevent Word from loading RTF files

For Word 2003 Interactive

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2003Managed Deployment Script

If you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

For Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

If the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:

a. Select the Security subkey.
b. On the Edit menu, point to New, and then click Key.
c. Type FileOpenBlock, and then press ENTER.

After you select the FileOpenBlock subkey, locate the DWORD value RtfFiles.Note If this value does not exist, you must create it. To do this, follow these steps:

a. On the Edit menu, point to New, and then click DWORD Value.
b. Type RtfFiles and then press ENTER.

Right-click RtfFiles and then click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

For Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Disable_RTF_In_Word.reg

Impact of workaround. RTF files will not be readable by Word.

How to undo the workaround.

Rollback for Word 2003 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2003 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg

Rollback for Word 2007 Interactive

Click Start, click Run, type regedit in the Open box, and then click OK.

Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock

.Right-click RtfFiles and then click Delete.

.In the Confirm Value Delete dialog box, click Yes.

.On the File menu, click Exit to exit Registry Editor.

Rollback for Word 2007 Managed Deployment Script

Save the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-

Run the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:

Regedit /s Enable_RTF_In_Word.reg
•

Read e-mails in plain text

For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
•

The changes are applied to the preview pane and to open messages.
•

Pictures become attachments so that they are not lost.
•

Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
Top of sectionTop of section

FAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4031

What causes the vulnerability?
The vulnerability is caused by a memory calculation error when processing a malformed string in a specially crafted RTF file. The error 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 control of an affected system in the context of the currently logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system.

Note By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.

What does the update do?
The update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.

Word Memory Corruption Vulnerability - CVE-2008-4837

A remote code execution vulnerability exists in the way that Microsoft Office Word handles specially crafted Word files. The vulnerability could allow remote code execution if a user opens a specially crafted Word file that includes a malformed record value. An attacker who successfully exploited this vulnerability could take control of an affected system in the context of the current logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

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

Mitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4837

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
•

Workarounds for Word Memory Corruption Vulnerability - CVE-2008-4837

On Word client systems, use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or un-trusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

ASSOC .doc=oice.word.document

ASSOC .doc=Word.Document.8

Note On Windows Vista and Windows Server 2008, the commands will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

FAQ for Word Memory Corruption Vulnerability - CVE-2008-4837

What causes the vulnerability?
When a user opens a specially crafted Office 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 run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. 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.

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word file to the user and by convincing the user to open the file.

Other Information
Acknowledgments

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

Ricardo Narvaja of Core Security Technologies for reporting the Word Memory Corruption Vulnerability (CVE-2008-4024)
•

Dyon Balding of Secunia Research for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4025)
•

Yamata Li of Palo Alto Networks for reporting the Word Memory Corruption Vulnerability (CVE-2008-4026)
•

Wushi, working with TippingPoint and the Zero Day Initiative, for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4027)
•

Aaron Portnoy of TippingPoint DVLabs for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4030)
•

Wushi of team509, working with Zero Day Initiative, for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4028)
•

Aaron Portnoy of TippingPoint DVLabs for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4031)
•

Wushi and Ling, working with TippingPoint and the Zero Day Initiative, for reporting the Word Memory Corruption Vulnerability (CVE-2008-4837)
Top of sectionTop of section
Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Top of sectionTop of section
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.
Top of sectionTop of section
Revisions
•

V1.0 (December 9, 2008): Bulletin published.