|
|
|
|
| |
Credit:
The information has been provided by Microsoft Product Security.
The original article can be found at: http://www.microsoft.com/technet/security/bulletin/MS08-014.mspx
|
| |
Affected Software:
Office Suite and Other Software - Component - Maximum Security Impact - Aggregate Severity Rating - Bulletins Replaced by This Update
* Microsoft Office 2000 Service Pack 3 - Excel 2000 Service Pack 3 (KB946979) - Remote Code Execution - Critical - MS07-044
* Microsoft Office XP Service Pack 3 - Excel 2002 Service Pack 3 (KB946976) - Remote Code Execution - Important - MS07-044
* Microsoft Office 2003 Service Pack 2 - Excel 2003 Service Pack 2 (KB943985) - Remote Code Execution - Important - MS07-044
* 2007 Microsoft Office System - Excel 2007 (KB946974) - Remote Code Execution - Important - MS07-036
* Microsoft Office Excel Viewer 2003 (KB943889) - - Remote Code Execution - Important - MS07-044
* Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (KB947801) - - Remote Code Execution - Important - MS07-036
* Microsoft Office 2004 for Mac (KB949357) - - Remote Code Execution - Important - MS08-013
* Microsoft Office 2008 for Mac (KB948057) - - Remote Code Execution - Important - None
Non-Affected Software:
Office Suite and Other Software - Component
* Microsoft Office 2003 Service Pack 3 - Excel 2003 Service Pack 3
* 2007 Microsoft Office System Service Pack 1 - Excel 2007 Service Pack 1
* Microsoft Works 8.0
* Microsoft Works 8.5
* Microsoft Works 9.0
* Microsoft Works Suite 2005
* Microsoft Works Suite 2006
Excel Data Validation Record Vulnerability - CVE-2008-0111
A remote code execution vulnerability exists in the way Excel processes data validation records when loading Excel files into memory. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0111
Excel File Import Vulnerability - CVE-2008-0112
A remote code execution vulnerability exists in the way Excel handles data when importing files into Excel. An attacker could exploit the vulnerability by sending a malformed .slk file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment, and which could then be imported into Excel.
CVE Information:
CVE-2008-0112
Excel Style Record Vulnerability - CVE-2008-0114
A remote code execution vulnerability exists in the way Excel handles Style record data when opening Excel files. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0114
Excel Formula Parsing Vulnerability - CVE-2008-0115
A remote code execution vulnerability exists in the way Excel handles malformed formulas. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0115
Excel Rich Text Validation Vulnerability - CVE-2008-0116
A remote code execution vulnerability exists in the way Excel handles rich text values when loading application data into memory. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0116
Excel Conditional Formatting Vulnerability - CVE-2008-0117
A remote code execution vulnerability exists in the way Excel handles conditional formatting values. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0117
Macro Validation Vulnerability - CVE-2008-0081
A remote code execution vulnerability exists in the way Excel handles macros when opening specially crafted Excel files. An attacker could exploit the vulnerability by sending a malformed file which could be hosted on a specially crafted or compromised Web site, or included as an e-mail attachment.
CVE Information:
CVE-2008-0081
Workarounds:
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 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 File Format Converters.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 handle 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 .XLS=oice.excel.sheet - ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template - ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin - ASSOC .xla=Excel.Addin
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.
Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations
The following registry scripts can be used to set the File Block policy.
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 Office 2003
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock]
"BinaryFiles"=dword:00000001
Note In order to use 'FileOpenBlock' with Office 2003, all of the latest Office 2003 security updates must be applied.
Impact of Workaround: Users who have configured the File Block policy and have not configured a special exempt directory as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.
How to Undo the Workaround:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock]
"BinaryFiles"=dword:00000000
|
|
|
|
|
