Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Windows RiсhEdit control memory corruption

From:MICROSOFT <secure_(at)_microsoft.com>
Date:13.02.2007
Subject:Microsoft Security Bulletin MS07-013 Vulnerability in Microsoft RichEdit Could Allow Remote Code Execution (918118)

Microsoft Security Bulletin MS07-013
Vulnerability in Microsoft RichEdit Could Allow Remote Code Execution (918118)
Published: February 13, 2007

Version: 1.0
Summary

Who Should Read this Document: Customers who use Microsoft Windows and/or Microsoft Office

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Important

Recommendation: Customers should apply the update at the earliest opportunity

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

Windows Software:


Microsoft Windows 2000 Service Pack 4 — Download the update


Microsoft Windows XP Service Pack 2 — Download the update


Microsoft Windows XP Professional x64 Edition — Download the update


Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 — Download the update


Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems — Download the update


Microsoft Windows Server 2003 x64 Edition — Download the update

Office Software:


Microsoft Office 2000 Service Pack 3 — Download the update (KB920906)


Microsoft Access 2000


Microsoft Excel 2000


Microsoft FrontPage 2000


Microsoft Outlook 2000


Microsoft PowerPoint 2000


Microsoft Publisher 2000


Microsoft Word 2000


Microsoft Office XP Service Pack 3 — Download the update (KB920816)


Microsoft Access 2002


Microsoft Excel 2002


Microsoft FrontPage 2002


Microsoft Outlook 2002


Microsoft PowerPoint 2002


Microsoft Publisher 2002


Microsoft Word 2002


Microsoft Office 2003 Service Pack 2 — Download the update (KB920813)


Microsoft Access 2003


Microsoft Excel 2003


Microsoft FrontPage 2003


Microsoft InfoPath 2003


Microsoft OneNote 2003


Microsoft Outlook 2003


Microsoft PowerPoint 2003


Microsoft Project 2003


Microsoft Publisher 2003


Microsoft Visio 2003


Microsoft Word 2003


Microsoft Word 2003 Viewer


Microsoft Project 2000 Service Release 1 - Download the update (KB920906)


Microsoft Office 2000 Multilanguage Packs — Download the update (KB920906)


Microsoft Project 2002 Service Pack 1 - Download the update (KB920816)


Microsoft Visio 2002 Service Pack 2 - Download the update (KB920816)


Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office - Download the update (KB929437)


Microsoft Global Input Method Editor for Office 2000 (Japanese) - Download the update (KB920906)


Microsoft Office 2004 for Mac - Download the update (KB932185)

Non-Affected Software:


Windows Vista


2007 Microsoft Office System


Microsoft Office 2003 Service Pack 2


Microsoft Excel 2003 Viewer


Microsoft PowerPoint 2003 Viewer

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
Top of sectionTop of section
General Information

Executive Summary

Executive Summary:

This update addresses a newly discovered, privately reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

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

We recommend that customers apply the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers Impact of Vulnerability Microsoft Office 2000, Microsoft Office XP, and Microsoft Office 2003 Learning Essentials 1.0, 1.1, 1.5 for Microsoft Office, and Microsoft Global Input Method Editor for Office 2000 (Japanese) Microsoft Office 2004 for Mac Microsoft Windows 2000 Service Pack 4 Microsoft Windows XP Service Pack 2 Microsoft Windows Server 2003 (All Versions)

Microsoft RichEdit Vulnerability - CVE-2006-1311


Remote Code Execution


Important


Important


Important


Important


Important


Important

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The severity ratings for Project 2002, Visio 2002, Project 2000, Office 2000 Multilanguage packs, and Global Input Method Editor for Office map to the Office 2000, Office XP and Office 2003 applications.

Note The security updates for Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:


The Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.


The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.


The Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.


The Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 severity rating.
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

Does this security update remove the same vulnerability as those addressed in MS07-011 and MS07-012?
No, each individual security bulletin addresses unique security vulnerabilities in different software components; however, similarities do exist between the three security bulletins in how an attacker could exploit the vulnerabilities. It should be noted that MS07-011 (OLE) includes a defense-in-depth improvement that help block known attack vectors to the vulnerability addressed in MS07-012 (MFC). Even with the MS07-011 defense-in-depth improvement, Microsoft strongly that all three security updates be deployed to address all known vulnerabilities.

Do I need to deploy this security update before MS07-011 and MS07-012?
No, the security updates in the three security bulletins can be deployed in any order. There are no application compatibility dependencies between the security updates in the three security bulletins.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
Product MBSA 1.2.1 MBSA 2.0

Microsoft Office 2000 Service Pack 3


Yes (ODT)


No

Microsoft Office XP Service Pack 3


Yes (ODT)


Yes

Microsoft Office 2003 Service Pack 2


Yes (ODT)


Yes

Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office


Yes (ODT)


Yes

Microsoft Office 2004 for Mac


No


No

Microsoft Windows 2000 Service Pack 4


Yes


Yes

Microsoft Windows XP Service Pack 2


Yes


Yes

Microsoft Windows XP Professional x64 Edition


No


Yes

Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1


Yes


Yes

Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems


No


Yes

Microsoft Windows Server 2003 x64 Edition family


No


Yes

Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.

For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

For more detailed information, see Microsoft Knowledge Base Article 910723.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
Software SMS 2.0 SMS 2003

Microsoft Office 2000 Service Pack 3


Yes


Yes

Microsoft Office XP Service Pack 3


Yes


Yes

Microsoft Office 2003 Service Pack 2


Yes


Yes

Microsoft Learning Essentials 1.0, 1.1, and 1.5 for Microsoft Office


Yes


Yes

Microsoft Office 2004 for Mac


No


No

Microsoft Windows 2000 Service Pack 4


Yes


Yes

Microsoft Windows XP Service Pack 2


Yes


Yes

Microsoft Windows XP Professional x64 Edition


No


Yes

Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1


Yes


Yes

Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems


No


Yes

Microsoft Windows Server 2003 x64 Edition family


No


Yes

SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

Note If you have used an Administrative Installation Point for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline.


For more information about how to change the source for a client computer from an updated administrative installation point to an Office 2000 original baseline source or Service Pack 3 (SP3) see, Microsoft Knowledge Base Article 932889.


For more information on how to change the source for a client computer from an updated administrative installation point to an Office XP original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 922665.


For more information about how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 2 (SP2) see, Microsoft Knowledge Base Article 902349.

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

Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1 has reached the end of its support life cycle. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do?
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems; what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for these products 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 the Microsoft Worldwide Information Web site, 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 Details

Microsoft RichEdit Vulnerability - CVE-2006-1311:

A remote code execution vulnerability exists in the RichEdit components provided with Microsoft Windows and Microsoft Office. An attacker could exploit this vulnerability when a user interacts with a malformed embedded OLE object within a Rich Text Format (RTF) file.

If a 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 full user rights. 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.

Mitigating Factors for Microsoft RichEdit Vulnerability - CVE-2006-1311:


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.


An attacker could only exploit this vulnerability when a user opens and then interacts with the embedded OLE object within an RTF file.


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


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 and then interact with the embedded OLE object within an RTF file.
Top of sectionTop of section

Workarounds for Microsoft RichEdit Vulnerability - CVE-2006-1311:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.


Enable Embedded Object blocking in WordPad

Note: This workaround only applies to Microsoft Windows XP Service Pack 2, Microsoft Windows Server 2003, and Microsoft Windows Server 2003 Service Pack 1 systems.

Wordpad.exe is the default application used to open Rich Text files. Users can temporarily block the parsing of embedded objects within Rich Text Files.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

We recommend that you back up the registry before you edit it.

Use the following text to create a .reg file that will automate editing of the registry to temporarily block the parsing of embedded objects with Rich Text Files when using Wordpad.exe. You can copy the following text, paste it into a text editor such as Notepad, and then save the file with the .reg file name extension. Run the .reg file on the vulnerable client.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RtfStreamIn\ObjectBlocking
\wordpad.exe]

Impact of Workaround: Wordpad.exe will no longer parse embedded objects within Rich Text files.


Do not open or save RTF 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.


Un-install WordPad from Windows 2000 or Windows 2003

Wordpad.exe is the default application used to open Rich Text files. By uninstalling WordPad, users can block the parsing of embedded objects within Rich Text Files.

1.


Click Start, click Control Panel, and then click Add or Remove Programs.

2.


Click Add/Remove Windows Components, double-click Accessories and Utilities, and then double-click Accessories.

3.


Uncheck Wordpad, click Okay to let the Optional Component manager uninstall Wordpad.

Impact of Workaround: Wordpad will no longer parse embedded objects within Rich Text files.
Top of sectionTop of section

FAQ for Microsoft RichEdit Vulnerability - CVE-2006-1311:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in the RichEdit components provided with Microsoft Windows and Microsoft Office. An attacker could exploit this vulnerability when a user interacts with a malformed embedded OLE object within a Rich Text format.

If a 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 full user rights. 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 is Rich Text Format (RTF)?
The Rich Text Format (RTF) Specification provides a format for text and graphics interchange that can be used with different output devices, operating environments, and operating systems.

What is OLE?
By using OLE technology, an application can provide embedding and linking support. OLE is the technology that applications use to create and edit compound documents. These are documents of one format, such as a Microsoft Word document, that contain embeddings of (or links to) documents of another format, such as Microsoft Excel. OLE 2.0 takes OLE even further by allowing in-place editing. Instead of launching a new application when an OLE object is activated, the user instead sees a new set of menu items inside their existing application. For more information about OLE, visit the following Microsoft Web site.

What causes the vulnerability?
Microsoft Windows and Office RichEdit components do not perform sufficient validation when parsing OLE objects embedded within RTF files. When a user interacts with a malformed embedded OLE Object within an RTF 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 cause arbitrary code to run with the privileges of the user who opened the file.

How could an attacker exploit the vulnerability?
An attacker could only exploit this vulnerability when a user opens and then interacts with an embedded OLE object within an RTF file.

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

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 and then interact with the embedded OLE object within an RTF file.

What systems are primarily at risk from the vulnerability?
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 the Microsoft Windows and Office RichEdit components parse OLE streams within RTF.

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.

Acknowledgments

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


Kostya Kortchinsky of Immunity, Inc and Fabrice Desclaux of EADS Common Research Center for reporting the Microsoft RichEdit Vulnerability (CVE-2006-1311).


Revisions:


V1.0 (February 13, 2007): Bulletin published.

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