ID CVE-2008-4027 Type cve Reporter cve@mitre.org Modified 2018-10-30T16:25:00
Description
Double free vulnerability in Microsoft Office Word 2000 SP3, 2002 SP3, 2003 SP3, and 2007 Gold and SP1; Outlook 2007 Gold and SP1; Word Viewer 2003 Gold and SP3; Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Gold and SP1; and Office 2004 for Mac allow remote attackers to execute arbitrary code via a crafted (1) RTF file or (2) rich text e-mail message with multiple consecutive Drawing Object ("\do") tags, which triggers a "memory calculation error" and memory corruption, aka "Word RTF Object Parsing Vulnerability."
{"zdi": [{"lastseen": "2016-11-09T00:18:05", "bulletinFamily": "info", "description": "This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Microsoft Office. User interaction is required to exploit this vulnerability in that the target must visit a malicious page, open a malicious e-mail, or open a malicious file.\n\nThe specific flaw exists when parsing malformed RTF documents. When processing consecutive \"\\do\" Drawing Object tags mso.dll does not properly verify the integrity of the object and frees a memory buffer twice, leading to heap corruption. Successful exploitation can lead to remote compromise of a system under the credentials of the currently logged in user.", "modified": "2008-11-09T00:00:00", "published": "2008-12-09T00:00:00", "href": "http://www.zerodayinitiative.com/advisories/ZDI-08-084", "id": "ZDI-08-084", "title": "Microsoft Office RTF Consecutive Drawing Object Parsing Heap Corruption Vulnerability", "type": "zdi", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:28", "bulletinFamily": "software", "description": "ZDI-08-084: Microsoft Office RTF Consecutive Drawing Object Parsing Heap \r\nCorruption Vulnerability\r\nhttp://www.zerodayinitiative.com/advisories/ZDI-08-084\r\nDecember 9, 2008\r\n\r\n-- CVE ID:\r\nCVE-2008-4027\r\n\r\n-- Affected Vendors:\r\nMicrosoft\r\n\r\n-- Affected Products:\r\nMicrosoft Office Word\r\nMicrosoft Outlook\r\n\r\n-- TippingPoint(TM) IPS Customer Protection:\r\nTippingPoint IPS customers have been protected against this\r\nvulnerability by Digital Vaccine protection filter ID 6607. \r\nFor further product information on the TippingPoint IPS, visit:\r\n\r\n http://www.tippingpoint.com\r\n\r\n-- Vulnerability Details:\r\nThis vulnerability allows remote attackers to execute arbitrary code on\r\nvulnerable installations of Microsoft Office. User interaction is\r\nrequired to exploit this vulnerability in that the target must visit a\r\nmalicious page, open a malicious e-mail, or open a malicious file.\r\n\r\nThe specific flaw exists when parsing malformed RTF documents. When\r\nprocessing consecutive "\do" Drawing Object tags mso.dll does not\r\nproperly verify the integrity of the object and frees a memory buffer\r\ntwice, leading to heap corruption. Successful exploitation can lead to\r\nremote compromise of a system under the credentials of the currently\r\nlogged in user.\r\n\r\n-- Vendor Response:\r\nMicrosoft has issued an update to correct this vulnerability. More\r\ndetails can be found at:\r\n\r\nhttp://www.microsoft.com/technet/security/bulletin/MS08-072.mspx\r\n\r\n-- Disclosure Timeline:\r\n2008-05-19 - Vulnerability reported to vendor\r\n2008-12-09 - Coordinated public release of advisory\r\n\r\n-- Credit:\r\nThis vulnerability was discovered by:\r\n * wushi of team509\r\n\r\n-- About the Zero Day Initiative (ZDI):\r\nEstablished by TippingPoint, The Zero Day Initiative (ZDI) represents \r\na best-of-breed model for rewarding security researchers for responsibly\r\ndisclosing discovered vulnerabilities.\r\n\r\nResearchers interested in getting paid for their security research\r\nthrough the ZDI can find more information and sign-up at:\r\n\r\n http://www.zerodayinitiative.com\r\n\r\nThe ZDI is unique in how the acquired vulnerability information is\r\nused. TippingPoint does not re-sell the vulnerability details or any\r\nexploit code. Instead, upon notifying the affected product vendor,\r\nTippingPoint provides its customers with zero day protection through\r\nits intrusion prevention technology. Explicit details regarding the\r\nspecifics of the vulnerability are not exposed to any parties until\r\nan official vendor patch is publicly available. Furthermore, with the\r\naltruistic aim of helping to secure a broader user base, TippingPoint\r\nprovides this vulnerability information confidentially to security\r\nvendors (including competitors) who have a vulnerability protection or\r\nmitigation product.\r\n\r\nOur vulnerability disclosure policy is available online at:\r\n\r\n http://www.zerodayinitiative.com/advisories/disclosure_policy/\r\n\r\nCONFIDENTIALITY NOTICE: This e-mail message, including any attachments,\r\nis being sent by 3Com for the sole use of the intended recipient(s) and\r\nmay contain confidential, proprietary and/or privileged information.\r\nAny unauthorized review, use, disclosure and/or distribution by any \r\nrecipient is prohibited. If you are not the intended recipient, please\r\ndelete and/or destroy all copies of this message regardless of form and\r\nany included attachments and notify 3Com immediately by contacting the\r\nsender via reply e-mail or forwarding to 3Com at postmaster@3com.com. ", "modified": "2008-12-10T00:00:00", "published": "2008-12-10T00:00:00", "id": "SECURITYVULNS:DOC:20974", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:20974", "title": "ZDI-08-084: Microsoft Office RTF Consecutive Drawing Object Parsing Heap Corruption Vulnerability", "type": "securityvulns", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2018-08-31T11:10:28", "bulletinFamily": "software", "description": "Microsoft Security Bulletin MS08-072 - Critical\r\nVulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)\r\nPublished: December 9, 2008\r\n\r\nVersion: 1.0\r\nGeneral Information\r\nExecutive Summary\r\n\r\nThis 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.\r\n\r\nThis 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.\r\n\r\nThe 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.\r\n\r\nRecommendation. Microsoft recommends that customers apply the update immediately.\r\n\r\nKnown 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.\r\nTop of sectionTop of section\r\nAffected and Non-Affected Software\r\n\r\nThe 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.\r\n\r\nAffected Software \r\nOffice Suite and Other Software\tComponent\tMaximum Security Impact\tAggregate Severity Rating\tBulletins Replaced by this Update\r\nMicrosoft Office Suites and Components\t \t \t \t \r\n\r\nMicrosoft Office 2000 Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Word 2000 Service Pack 3\r\n(KB956328)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nMS08-026\r\n\r\nMicrosoft Office XP Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Word 2002 Service Pack 3\r\n(KB956329)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-042\r\n\r\nMicrosoft Office 2003 Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Word 2003 Service Pack 3\r\n(KB956357)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-042\r\n\r\n2007 Microsoft Office System\r\n\t\r\n\r\nMicrosoft Office Word 2007\r\n(KB956358)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\n2007 Microsoft Office System\r\n\t\r\n\r\nMicrosoft Office Outlook 2007\r\n(KB956358)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nNone\r\n\r\n2007 Microsoft Office System Service Pack 1\r\n\t\r\n\r\nMicrosoft Office Word 2007 Service Pack 1\r\n(KB956358)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\n2007 Microsoft Office System Service Pack 1\r\n\t\r\n\r\nMicrosoft Office Outlook 2007 Service Pack 1\r\n(KB956358)\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nNone\r\nOther Office Software\t \t \t \t \r\n\r\nMicrosoft Office Word Viewer 2003\r\n(KB956366)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\nMicrosoft Office Word Viewer 2003 Service Pack 3\r\n(KB956366)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats\r\n(KB956828)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1\r\n(KB956828)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-026\r\n\r\nMicrosoft Works 8*\r\n(KB959487)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-052\r\nMicrosoft Office for Mac\t \t \t \t \r\n\r\nMicrosoft Office 2004 for Mac\r\n(KB960402)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-057\r\n\r\nMicrosoft Office 2008 for Mac\r\n(KB960401)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-057\r\n\r\nOpen XML File Format Converter for Mac\r\n(KB960403)\r\n\t\r\n\r\nNot applicable \r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS08-057\r\n\r\n*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.\r\n\r\nNon-Affected Software \r\nOffice and Other Software\tComponent\r\n\r\nMicrosoft Office 2000 Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Outlook 2000 Service Pack 3\r\n\r\nMicrosoft Office XP Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Outlook 2002 Service Pack 3\r\n\r\nMicrosoft Office 2003 Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Outlook 2003 Service Pack 3\r\n\r\nMicrosoft Works 9.0\r\n\t\r\n\r\nNot applicable \r\nTop of sectionTop of section\r\n\t\r\nFrequently Asked Questions (FAQ) Related to This Security Update\r\n\r\nWhere are the file information details? \r\nThe file information details can be found in Microsoft Knowledge Base Article 957173.\r\n\r\nMS08-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)? \r\nThis 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.\r\n\r\nWhy does this update address several reported security vulnerabilities? \r\nThis 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.\r\n\r\nWhy is this update rated Critical for Outlook 2007?\r\nOutlook 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.\r\n\r\nWhy is this update Critical for Word 2000 but only Important for all other affected versions of Word?\r\nMicrosoft 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.\r\n\r\nThis 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?\r\nThe 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.\r\n\r\nUsers 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.\r\n\r\nI am using Works 8.0, how do I update to Works 8.5?\r\nMicrosoft 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.\r\n\r\nHow do I know if I need to update my version of Works? \r\nFind 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.\r\n\r\nWhat components of the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats are updated by this bulletin? \r\nThe 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.\r\n\r\nThe 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?\r\nYes, 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.\r\n\r\nDoes the offer to update a non-vulnerable version of Microsoft Office constitute an issue in the Microsoft update mechanism?\r\nNo, 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.\r\n\r\nI use Microsoft Office 2007 RTM. Are any additional security features included in this update?\r\nYes, 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.\r\n\r\nI am using an older release of the software discussed in this security bulletin. What should I do? \r\nThe 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.\r\n\r\nIt 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.\r\n\r\nCustomers 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.\r\nTop of sectionTop of section\r\nVulnerability Information\r\n\t\r\nSeverity Ratings and Vulnerability Identifiers\r\nVulnerability Severity Rating and Maximum Security Impact by Affected Software\r\nAffected Software\tWord Memory Corruption Vulnerability - CVE-2008-4024\tWord RTF Object Parsing Vulnerability - CVE-2008-4025 \tWord Memory Corruption Vulnerability - CVE-2008-4026\tWord RTF Object Parsing Vulnerability - CVE-2008-4027\tWord RTF Object Parsing Vulnerability - CVE-2008-4030\tWord RTF Object Parsing Vulnerability - CVE-2008-4028\tWord RTF Object Parsing Vulnerability - CVE-2008-4031\tWord Memory Corruption Vulnerability - CVE-2008-4837\tAggregate Severity Rating\r\nOffice Software\t \t \t \t \t \t \t \t \t \r\n\r\nMicrosoft Office Word 2000 Service Pack 3\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\r\nMicrosoft Office Word 2002 Service Pack 3\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office Word 2003 Service Pack 3\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office Word 2007\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nOutlook 2007\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\r\nMicrosoft Office Word 2007 Service Pack 1\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\n \r\n\r\nOutlook 2007 Service Pack 1\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical \r\nRemote Code Execution\r\n\r\nMicrosoft Office Word Viewer 2003\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office Word Viewer 2003 Service Pack 3\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Works 8\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office 2004 for Mac\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nMicrosoft Office 2008 for Mac\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\r\nOpen XML File Format Converter for Mac\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nImportant\r\nRemote Code Execution\r\nTop of sectionTop of section\r\n\r\n\t\r\nWord Memory Corruption Vulnerability - CVE-2008-4024\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4024.\r\n\t\r\nMitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4024\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nThe 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.\r\n\u2022\t\r\n\r\nIn 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.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word Memory Corruption Vulnerability - CVE-2008-4024\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nDo 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.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word Memory Corruption Vulnerability - CVE-2008-4024\r\n\r\nWhat is the scope of the vulnerability? \r\nThis is a remote code execution vulnerability. 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.\r\n\r\nWhat causes the vulnerability? \r\nWhen a user opens a specially crafted Office file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.\r\n\r\nIn 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.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe 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.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord RTF Object Parsing Vulnerability - CVE-2008-4025\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4025.\r\n\t\r\nMitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4025\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site, and then convincing them to open the specially crafted RTF file.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4025\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nPrevent Word from loading RTF files\r\n\r\nNote 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.\r\n\r\nFor Word 2003 Interactive\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2003Managed Deployment Script\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nFor Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nImpact of workaround. RTF files will not be readable by Word.\r\n\r\nHow to undo the workaround.\r\n\r\nRollback for Word 2003 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2003 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\r\nRollback for Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\u2022\t\r\n\r\nRead e-mails in plain text\r\n\r\nRead 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.\r\n\r\nMicrosoft 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.\r\n\r\nDigitally 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.\r\n\r\nFor information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.\r\n\r\nImpact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4025\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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.\r\n\r\nWhat causes the vulnerability? \r\nThe 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.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis 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.\r\n\r\nIn 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.\r\n\r\nNote By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord Memory Corruption Vulnerability - CVE-2008-4026\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4026.\r\n\t\r\nMitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4026\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nUsers 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 later editions of Office.\r\n\u2022\t\r\n\r\nThe 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site., and then convincing them to open the specially crafted Word file\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word Memory Corruption Vulnerability - CVE-2008-4026\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nDo 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.\r\n\u2022\t\r\n\r\nOn Word client systems, use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or un-trusted sources\r\n\r\nThe Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.\r\n\r\nTo install MOICE, you must have Office 2003 or 2007 Office system installed.\r\n\r\nTo 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:\r\n\r\nDownload the FileFormatConverters.exe package now\r\n\r\nMOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:\r\n\r\nhttp://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us\r\n\r\nTo 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:\r\nCommand to use to enable MOICE to be the registered handler\tCommand to use to disable MOICE as the registered handler\r\n\r\nASSOC .doc=oice.word.document\r\n\t\r\n\r\nASSOC .doc=Word.Document.8\r\n\r\nNote On Windows Vista and Windows Server 2008, the commands will need to be run from an elevated command prompt.\r\n\r\nFor more information on MOICE, see Microsoft Knowledge Base Article 935865.\r\n\r\nImpact 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.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word Memory Corruption Vulnerability - CVE-2008-4026\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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.\r\n\r\nWhat causes the vulnerability? \r\nWhen a user opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.\r\n\r\nIn 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.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe 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.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord RTF Object Parsing Vulnerability - CVE-2008-4027\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4027.\r\n\t\r\nMitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4027\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site, and then convincing them to open the specially crafted Word file.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4027\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nPrevent Word from loading RTF files\r\n\r\nNote 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.\r\n\r\nFor Word 2003 Interactive\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2003Managed Deployment Script\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nFor Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nImpact of workaround. RTF files will not be readable by Word.\r\n\r\nHow to undo the workaround.\r\n\r\nRollback for Word 2003 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2003 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\r\nRollback for Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\u2022\t\r\n\r\nRead e-mails in plain text\r\n\r\nRead 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.\r\n\r\nMicrosoft 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.\r\n\r\nDigitally 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.\r\n\r\nFor information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.\r\n\r\nImpact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4027\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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 logged in user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability? \r\nThe 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.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis 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.\r\n\r\nIn 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.\r\n\r\nNote By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by modifying the way Word cleans up memory after encountering malformed RTF content.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord RTF Object Parsing Vulnerability - CVE-2008-4030\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4030.\r\n\t\r\nMitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4030\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site, and then convincing them to open the specially crafted RTF file.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4030\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nPrevent Word from loading RTF files\r\n\r\nNote 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.\r\n\r\nFor Word 2003 Interactive\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2003Managed Deployment Script\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nFor Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nImpact of workaround. RTF files will not be readable by Word.\r\n\r\nHow to undo the workaround.\r\n\r\nRollback for Word 2003 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2003 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\r\nRollback for Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\u2022\t\r\n\r\nRead e-mails in plain text\r\n\r\nRead 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.\r\n\r\nMicrosoft 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.\r\n\r\nDigitally 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.\r\n\r\nFor information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.\r\n\r\nImpact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4030\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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.\r\n\r\nWhat causes the vulnerability? \r\nThe 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.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis 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.\r\n\r\nIn 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.\r\n\r\nNote By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord RTF Object Parsing Vulnerability - CVE-2008-4028\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4028.\r\n\t\r\nMitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4028\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site, and then convincing them to open the specially crafted RTF file.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4028\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nPrevent Word from loading RTF files\r\n\r\nNote 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.\r\n\r\nFor Word 2003 Interactive\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2003Managed Deployment Script\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nFor Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nImpact of workaround. RTF files will not be readable by Word.\r\n\r\nHow to undo the workaround.\r\n\r\nRollback for Word 2003 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2003 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\r\nRollback for Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\u2022\t\r\n\r\nRead e-mails in plain text\r\n\r\nRead 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.\r\n\r\nMicrosoft 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.\r\n\r\nDigitally 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.\r\n\r\nFor information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.\r\n\r\nImpact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4028\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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.\r\n\r\nWhat causes the vulnerability? \r\nThe 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.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis 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.\r\n\r\nIn 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 user reads or previews the e-mail.\r\n\r\nNote By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord RTF Object Parsing Vulnerability - CVE-2008-4031\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4031.\r\n\t\r\nMitigating Factors for Word RTF Object Parsing Vulnerability - CVE-2008-4031\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nIn 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\u2019s Web site, and then convincing them to open the specially crafted RTF file.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Object Parsing Vulnerability - CVE-2008-4031\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nPrevent Word from loading RTF files\r\n\r\nNote 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.\r\n\r\nFor Word 2003 Interactive\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2003Managed Deployment Script\r\n\r\nIf you have installed security update 934181, you can prevent this type of file from being loaded in Word 2003.\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nFor Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\nIf the FileOpenBlock subkey does not exist, you must create it. To do this, follow these steps:\r\n\r\na. Select the Security subkey.\r\nb. On the Edit menu, point to New, and then click Key.\r\nc. Type FileOpenBlock, and then press ENTER.\r\n\r\n3.\r\n\t\r\n\r\nAfter 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:\r\n\r\na. On the Edit menu, point to New, and then click DWORD Value.\r\nb. Type RtfFiles and then press ENTER.\r\n\r\n4.\r\n\t\r\n\r\nRight-click RtfFiles and then click Modify.\r\n\r\n5.\r\n\t\r\n\r\nIn the Value data box, type 1, and then click OK.\r\n\r\n6.\r\n\t\r\n\r\nOn the File menu, click Exit to exit Registry Editor.\r\n\r\nFor Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Disable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=dword:00000001\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Disable_RTF_In_Word.reg\r\n\r\nImpact of workaround. RTF files will not be readable by Word.\r\n\r\nHow to undo the workaround.\r\n\r\nRollback for Word 2003 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2003 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\r\nRollback for Word 2007 Interactive\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type regedit in the Open box, and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nLocate and then click the following registry subkey:\r\n\r\nHKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock\r\n\r\n3.\r\n\t\r\n\r\n.Right-click RtfFiles and then click Delete.\r\n\r\n4.\r\n\t\r\n\r\n.In the Confirm Value Delete dialog box, click Yes.\r\n\r\n5.\r\n\t\r\n\r\n.On the File menu, click Exit to exit Registry Editor.\r\n\r\nRollback for Word 2007 Managed Deployment Script\r\n\r\n1.\r\n\t\r\n\r\nSave the following to a file with a .REG extension (e.g. Enable_RTF_In_Word.reg):\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]"RtfFiles"=-\r\n\r\n2.\r\n\t\r\n\r\nRun the above registry script created in step 1 on the target machine with the following command from an administrator command prompt:\r\n\r\nRegedit /s Enable_RTF_In_Word.reg\r\n\u2022\t\r\n\r\nRead e-mails in plain text\r\n\r\nRead 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.\r\n\r\nMicrosoft 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.\r\n\r\nDigitally 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.\r\n\r\nFor information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.\r\n\r\nImpact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Object Parsing Vulnerability - CVE-2008-4031\r\n\r\nWhat is the scope of the vulnerability? \r\nThis 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.\r\n\r\nWhat causes the vulnerability? \r\nThe 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.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis 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.\r\n\r\nIn 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.\r\n\r\nNote By default, Outlook 2003 does not use Word as its default editor. However, Outlook 2007 does.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe update removes the vulnerability by modifying the way Word calculates the required memory allocation when opening RTF files.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord Memory Corruption Vulnerability - CVE-2008-4837\r\n\r\nA 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.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4837.\r\n\t\r\nMitigating Factors for Word Memory Corruption Vulnerability - CVE-2008-4837\r\n\r\nMitigation 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:\r\n\u2022\t\r\n\r\nAn 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.\r\n\u2022\t\r\n\r\nThe 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.\r\n\u2022\t\r\n\r\nIn 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.\r\n\u2022\t\r\n\r\nUsers 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.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word Memory Corruption Vulnerability - CVE-2008-4837\r\n\r\nWorkaround 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:\r\n\u2022\t\r\n\r\nDo 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.\r\n\u2022\t\r\n\r\nOn Word client systems, use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or un-trusted sources\r\n\r\nThe Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.\r\n\r\nTo install MOICE, you must have Office 2003 or 2007 Office system installed.\r\n\r\nTo 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:\r\n\r\nDownload the FileFormatConverters.exe package now\r\n\r\nMOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:\r\n\r\nhttp://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us\r\n\r\nTo 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:\r\nCommand to use to enable MOICE to be the registered handler\tCommand to use to disable MOICE as the registered handler\r\n\r\nASSOC .doc=oice.word.document\r\n\t\r\n\r\nASSOC .doc=Word.Document.8\r\n\r\nNote On Windows Vista and Windows Server 2008, the commands will need to be run from an elevated command prompt.\r\n\r\nFor more information on MOICE, see Microsoft Knowledge Base Article 935865.\r\n\r\nImpact 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.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word Memory Corruption Vulnerability - CVE-2008-4837\r\n\r\nWhat is the scope of the vulnerability? \r\nThis is a remote code execution vulnerability. 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.\r\n\r\nWhat causes the vulnerability? \r\nWhen a user opens a specially crafted Office file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.\r\n\r\nWhat might an attacker use the vulnerability to do? \r\nAn 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.\r\n\r\nHow could an attacker exploit the vulnerability? \r\nThis vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Office Word.\r\n\r\nIn 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.\r\n\r\nIn 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.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nSystems 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.\r\n\r\nWhat does the update do? \r\nThe 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.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. 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.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? \r\nNo. 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.\r\n\r\nOther Information\r\nAcknowledgments\r\n\r\nMicrosoft thanks the following for working with us to help protect customers:\r\n\u2022\t\r\n\r\nRicardo Narvaja of Core Security Technologies for reporting the Word Memory Corruption Vulnerability (CVE-2008-4024)\r\n\u2022\t\r\n\r\nDyon Balding of Secunia Research for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4025)\r\n\u2022\t\r\n\r\nYamata Li of Palo Alto Networks for reporting the Word Memory Corruption Vulnerability (CVE-2008-4026)\r\n\u2022\t\r\n\r\nWushi, working with TippingPoint and the Zero Day Initiative, for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4027)\r\n\u2022\t\r\n\r\nAaron Portnoy of TippingPoint DVLabs for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4030)\r\n\u2022\t\r\n\r\nWushi of team509, working with Zero Day Initiative, for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4028)\r\n\u2022\t\r\n\r\nAaron Portnoy of TippingPoint DVLabs for reporting the Word RTF Object Parsing Vulnerability (CVE-2008-4031)\r\n\u2022\t\r\n\r\nWushi and Ling, working with TippingPoint and the Zero Day Initiative, for reporting the Word Memory Corruption Vulnerability (CVE-2008-4837)\r\nTop of sectionTop of section\r\nMicrosoft Active Protections Program (MAPP)\r\n\r\nTo 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.\r\nTop of sectionTop of section\r\nSupport\r\n\u2022\t\r\n\r\nCustomers 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.\r\n\u2022\t\r\n\r\nInternational 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.\r\n\r\nDisclaimer\r\n\r\nThe 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.\r\nTop of sectionTop of section\r\nRevisions\r\n\u2022\t\r\n\r\nV1.0 (December 9, 2008): Bulletin published.", "modified": "2008-12-10T00:00:00", "published": "2008-12-10T00:00:00", "id": "SECURITYVULNS:DOC:20970", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:20970", "title": "Microsoft Security Bulletin MS08-072 - Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)", "type": "securityvulns", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2018-08-31T11:09:31", "bulletinFamily": "software", "description": "Multiple memory corruptions on .doc and .xls parsing.", "modified": "2008-12-11T00:00:00", "published": "2008-12-11T00:00:00", "id": "SECURITYVULNS:VULN:9493", "href": "https://vulners.com/securityvulns/SECURITYVULNS:VULN:9493", "title": "Microsoft Office multiple security vulnerabilities", "type": "securityvulns", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "openvas": [{"lastseen": "2017-07-20T08:49:50", "bulletinFamily": "scanner", "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS08-072.", "modified": "2017-07-05T00:00:00", "published": "2008-12-10T00:00:00", "href": "http://plugins.openvas.org/nasl.php?oid=900063", "id": "OPENVAS:900063", "title": "Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: secpod_ms08-072.nasl 6538 2017-07-05 11:38:27Z cfischer $\n#\n# Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)\n#\n# Authors:\n# Chandan S <schandan@secpod.com>\n#\n# Make use of version_func_inc - By Chandan S, 11:48:13 2009/04/24\n#\n# Copyright: SecPod\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\ntag_impact = \"Successful exploitation could execute arbitrary code on the remote system\n and corrupt memory via a specially crafted Excel Spreadsheet (XLS) file.\n Impact Level: System\";\ntag_affected = \"Microsoft Office 2K/XP/2003/2007\";\ntag_insight = \"Microsoft office is prone to multiple vulnerabilities. For more information\n refer, http://secunia.com/advisories/30285/\";\ntag_solution = \"Run Windows Update and update the listed hotfixes or download and\n update mentioned hotfixes in the advisory from the below link.\n http://www.microsoft.com/technet/security/bulletin/ms08-072.mspx\";\ntag_summary = \"This host is missing a critical security update according to\n Microsoft Bulletin MS08-072.\";\n\n\nif(description)\n{\n script_id(900063);\n script_version(\"$Revision: 6538 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2017-07-05 13:38:27 +0200 (Wed, 05 Jul 2017) $\");\n script_tag(name:\"creation_date\", value:\"2008-12-10 17:58:14 +0100 (Wed, 10 Dec 2008)\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_cve_id(\"CVE-2008-4024\", \"CVE-2008-4025\", \"CVE-2008-4026\",\n \"CVE-2008-4027\", \"CVE-2008-4028\", \"CVE-2008-4030\",\n \"CVE-2008-4031\", \"CVE-2008-4837\");\n script_bugtraq_id(32579, 32580, 32581, 32583, 32584, 32585, 32594, 32642);\n script_name(\"Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)\");\n script_xref(name : \"URL\" , value : \"http://www.microsoft.com/technet/security/bulletin/ms08-072.mspx\");\n\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2008 SecPod\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"secpod_office_products_version_900032.nasl\", \"secpod_ms_office_detection_900025.nasl\");\n script_mandatory_keys(\"MS/Office/Ver\", \"SMB/Office/Word/Version\");\n\n script_tag(name : \"impact\" , value : tag_impact);\n script_tag(name : \"affected\" , value : tag_affected);\n script_tag(name : \"insight\" , value : tag_insight);\n script_tag(name : \"solution\" , value : tag_solution);\n script_tag(name : \"summary\" , value : tag_summary);\n script_tag(name:\"qod_type\", value:\"registry\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n exit(0);\n}\n\ninclude(\"version_func.inc\");\n\nif(egrep(pattern:\"^(9|10|11|12)\\..*\", string:get_kb_item(\"MS/Office/Ver\")))\n{\n wordVer = get_kb_item(\"SMB/Office/Word/Version\");\n if(!wordVer){\n exit(0);\n }\n\n if(version_in_range(version:wordVer, test_version:\"9.0\",\n test_version2:\"9.0.0.8973\")){\n security_message(0);\n }\n else if(version_in_range(version:wordVer, test_version:\"10.0\",\n test_version2:\"10.0.6849\")){\n security_message(0);\n }\n else if(version_in_range(version:wordVer, test_version:\"11.0\",\n test_version2:\"11.0.8236\")){\n security_message(0);\n }\n else if(version_in_range(version:wordVer, test_version:\"12.0\",\n test_version2:\"12.0.6331.4999\")){\n security_message(0);\n }\n}\n", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2019-05-29T18:40:26", "bulletinFamily": "scanner", "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS08-072.", "modified": "2019-05-03T00:00:00", "published": "2008-12-10T00:00:00", "id": "OPENVAS:1361412562310900063", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310900063", "title": "Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)", "type": "openvas", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n#\n# Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)\n#\n# Authors:\n# Chandan S <schandan@secpod.com>\n#\n# Make use of version_func_inc - By Chandan S, 11:48:13 2009/04/24\n#\n# Copyright: SecPod\n#\n# This program is free software; you can redistribute it and/or modify\n# it under the terms of the GNU General Public License version 2\n# (or any later version), as published by the Free Software Foundation.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.\n###############################################################################\n\nif(description)\n{\n script_oid(\"1.3.6.1.4.1.25623.1.0.900063\");\n script_version(\"2019-05-03T10:54:50+0000\");\n script_tag(name:\"last_modification\", value:\"2019-05-03 10:54:50 +0000 (Fri, 03 May 2019)\");\n script_tag(name:\"creation_date\", value:\"2008-12-10 17:58:14 +0100 (Wed, 10 Dec 2008)\");\n script_tag(name:\"cvss_base\", value:\"9.3\");\n script_tag(name:\"cvss_base_vector\", value:\"AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_cve_id(\"CVE-2008-4024\", \"CVE-2008-4025\", \"CVE-2008-4026\",\n \"CVE-2008-4027\", \"CVE-2008-4028\", \"CVE-2008-4030\",\n \"CVE-2008-4031\", \"CVE-2008-4837\");\n script_bugtraq_id(32579, 32580, 32581, 32583, 32584, 32585, 32594, 32642);\n script_name(\"Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (957173)\");\n script_xref(name:\"URL\", value:\"http://www.microsoft.com/technet/security/bulletin/ms08-072.mspx\");\n script_xref(name:\"URL\", value:\"http://secunia.com/advisories/30285/\");\n\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2008 SecPod\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"secpod_office_products_version_900032.nasl\", \"secpod_ms_office_detection_900025.nasl\");\n script_mandatory_keys(\"MS/Office/Ver\", \"SMB/Office/Word/Version\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation could execute arbitrary code on the remote system\n and corrupt memory via a specially crafted Excel Spreadsheet (XLS) file.\");\n\n script_tag(name:\"affected\", value:\"Microsoft Office 2K/XP/2003/2007\");\n\n script_tag(name:\"insight\", value:\"Microsoft office is prone to multiple vulnerabilities. Please see the\n references for more information.\");\n\n script_tag(name:\"solution\", value:\"The vendor has released updates. Please see the references for more information.\");\n\n script_tag(name:\"summary\", value:\"This host is missing a critical security update according to\n Microsoft Bulletin MS08-072.\");\n\n script_tag(name:\"qod_type\", value:\"registry\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n\n exit(0);\n}\n\ninclude(\"version_func.inc\");\n\nofficeVer = get_kb_item(\"MS/Office/Ver\");\n\nif(officeVer && officeVer =~ \"^(9|1[0-2])\\.\")\n{\n wordVer = get_kb_item(\"SMB/Office/Word/Version\");\n if(!wordVer || wordVer !~ \"^(9|1[0-2])\\.\"){\n exit(0);\n }\n\n if(version_in_range(version:wordVer, test_version:\"9.0\", test_version2:\"9.0.0.8973\")){\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n else if(version_in_range(version:wordVer, test_version:\"10.0\", test_version2:\"10.0.6849\")){\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n else if(version_in_range(version:wordVer, test_version:\"11.0\", test_version2:\"11.0.8236\")){\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n else if(version_in_range(version:wordVer, test_version:\"12.0\", test_version2:\"12.0.6331.4999\")){\n security_message( port: 0, data: \"The target host was found to be vulnerable\" );\n }\n}\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "nessus": [{"lastseen": "2019-02-21T01:13:59", "bulletinFamily": "scanner", "description": "The remote Mac OS X host is running a version of Microsoft Office that is affected by several vulnerabilities.\n\nIf an attacker can trick a user on the affected host into opening a specially crafted Excel or Word file, these issues could be leveraged to execute arbitrary code subject to the user's privileges.", "modified": "2018-07-14T00:00:00", "id": "MACOSX_MS_OFFICE_DEC2008.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=50060", "published": "2010-10-20T00:00:00", "title": "MS08-072 / MS08-074: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (957173 / 959070) (Mac OS X)", "type": "nessus", "sourceData": "#TRUSTED 202f2408a0efc3a371e6c11331aac07d873827194cb48bcbb767ee48f63d8c1aa3c9b9a458aa388a366dea0c469c82858042d839eb6ca266a9b312e8b7149bd12f1010280ad6778a5eda5bc56a62a0dc0e2573a7fa7523be26ba0b2bdcc553ede848e636ae0f28318ce62b2890a63656766f50bb287c97840b51985921e5d528ef5ee2feb0e15b462f72b57bf95e5269f681a0de7ada335ad841898ef0842de3a0abd28114aabdfed0368d33d9329286bb3b280ab88ee95d3546ad5a4f61e505473e709bcb98792630e5ab9315789f27edcc2587bcb32638fff6f347a70a836e0ce403ba38b4d44c260809046f38777825df587a99ae0e00ebb8f3f39e1113961208d5ff862591b2ce28e6efe6442b683d1e157f54a2710cddf10d89277613e9a2b3fd891550e0d7d26ae67774de703dd211ab674a06c4bee3e26a1c24dd151ca613c01a3eb153c3ecf105c51547f14d617bf79132cfcdc0d819b1e295af087b8f4dd841ff0682255fc0b9cdca9839a8cfbaead64a64ad481a96dbcf1311d8266dbd51b334a16b9de02c20250300d9face727aa8a534eec1a3ee04e94347fa1ae1a5ed182ebbf093e191255bf1f7eb0bd78663852a74e55a174c1712323d8f6fc5821a2ec7e520239f661efb7ba495f17449e5b4fce6bd9ff1f92f9874e8656c919a078fa07457d7949e2a9ae8ceaa5dce65f1d5b4f706a2323d90f7cda1b16a\n#\n# (C) Tenable Network Security, Inc.\n#\n\n\ninclude(\"compat.inc\");\n\n\nif (description)\n{\n script_id(50060);\n script_version(\"1.18\");\n script_set_attribute(attribute:\"plugin_modification_date\", value:\"2018/07/14\");\n\n script_cve_id(\n \"CVE-2008-4024\",\n \"CVE-2008-4025\",\n \"CVE-2008-4026\",\n \"CVE-2008-4027\",\n \"CVE-2008-4028\",\n \"CVE-2008-4031\",\n \"CVE-2008-4264\",\n \"CVE-2008-4266\"\n );\n script_bugtraq_id(\n 32579,\n 32580,\n 32581,\n 32583,\n 32585,\n 32594,\n 32621,\n 32622\n );\n script_xref(name:\"MSFT\", value:\"MS08-072\");\n script_xref(name:\"MSFT\", value:\"MS08-074\");\n script_xref(name:\"MSKB\", value:\"959070\");\n script_xref(name:\"MSKB\", value:\"957173\");\n script_xref(name:\"MSKB\", value:\"960401\");\n script_xref(name:\"MSKB\", value:\"960402\");\n script_xref(name:\"MSKB\", value:\"960403\");\n\n script_name(english:\"MS08-072 / MS08-074: Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (957173 / 959070) (Mac OS X)\");\n script_summary(english:\"Check version of Microsoft Office\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"An application installed on the remote Mac OS X host is affected by\nmultiple remote code execution vulnerabilities.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote Mac OS X host is running a version of Microsoft Office that\nis affected by several vulnerabilities.\n\nIf an attacker can trick a user on the affected host into opening a\nspecially crafted Excel or Word file, these issues could be leveraged\nto execute arbitrary code subject to the user's privileges.\");\n script_set_attribute(attribute:\"see_also\", value:\"http://technet.microsoft.com/en-us/security/bulletin/ms08-072\");\n script_set_attribute(attribute:\"see_also\", value:\"http://technet.microsoft.com/en-us/security/bulletin/ms08-074\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Office 2004 for Mac,\nOffice 2008 for Mac, and Open XML File Format Converter for Mac.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_cwe_id(399);\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2008/12/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2008/12/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2010/10/20\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:office:2004::mac\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:office:2008::mac\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:open_xml_file_format_converter:::mac\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n script_family(english:\"MacOS X Local Security Checks\");\n\n script_copyright(english:\"This script is Copyright (C) 2010-2018 Tenable Network Security, Inc.\");\n\n script_dependencies(\"ssh_get_info.nasl\");\n script_require_keys(\"Host/MacOSX/packages\", \"Host/uname\");\n\n exit(0);\n}\n\n\ninclude(\"misc_func.inc\");\ninclude(\"ssh_func.inc\");\ninclude(\"macosx_func.inc\");\n\n\n\nif(sshlib::get_support_level() >= sshlib::SSH_LIB_SUPPORTS_COMMANDS)\n enable_ssh_wrappers();\nelse disable_ssh_wrappers();\n\nfunction exec(cmd)\n{\n local_var buf, ret;\n\n if (islocalhost())\n buf = pread(cmd:\"/bin/bash\", argv:make_list(\"bash\", \"-c\", cmd));\n else\n {\n ret = ssh_open_connection();\n if (!ret) exit(1, \"ssh_open_connection() failed.\");\n buf = ssh_cmd(cmd:cmd);\n ssh_close_connection();\n }\n return buf;\n}\n\n\npackages = get_kb_item(\"Host/MacOSX/packages\");\nif (!packages) exit(1, \"The 'Host/MacOSX/packages' KB item is missing.\");\n\nuname = get_kb_item(\"Host/uname\");\nif (!uname) exit(1, \"The 'Host/uname' KB item is missing.\");\nif (!egrep(pattern:\"Darwin.*\", string:uname)) exit(1, \"The host does not appear to be using the Darwin sub-system.\");\n\n\n# Gather version info.\ninfo = '';\ninstalls = make_array();\n\nprod = 'Office 2008 for Mac';\nplist = \"/Applications/Microsoft Office 2008/Office/MicrosoftComponentPlugin.framework/Versions/12/Resources/Info.plist\";\ncmd = 'cat \\'' + plist + '\\' | ' +\n 'grep -A 1 CFBundleShortVersionString | ' +\n 'tail -n 1 | ' +\n 'sed \\'s/.*string>\\\\(.*\\\\)<\\\\/string>.*/\\\\1/g\\'';\nversion = exec(cmd:cmd);\nif (version && version =~ \"^[0-9]+\\.\")\n{\n version = chomp(version);\n if (version !~ \"^12\\.\") exit(1, \"Failed to get the version for \"+prod+\" - '\"+version+\"'.\");\n\n installs[prod] = version;\n\n ver = split(version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(ver); i++)\n ver[i] = int(ver[i]);\n\n fixed_version = '12.1.5';\n fix = split(fixed_version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(fix); i++)\n fix[i] = int(fix[i]);\n\n for (i=0; i<max_index(fix); i++)\n if ((ver[i] < fix[i]))\n {\n info +=\n '\\n Product : ' + prod +\n '\\n Installed version : ' + version +\n '\\n Fixed version : ' + fixed_version + '\\n';\n break;\n }\n else if (ver[i] > fix[i])\n break;\n}\n\nprod = 'Office 2004 for Mac';\ncmd = GetCarbonVersionCmd(file:\"Microsoft Component Plugin\", path:\"/Applications/Microsoft Office 2004/Office\");\nversion = exec(cmd:cmd);\nif (version && version =~ \"^[0-9]+\\.\")\n{\n version = chomp(version);\n if (version !~ \"^11\\.\") exit(1, \"Failed to get the version for \"+prod+\" - '\"+version+\"'.\");\n\n installs[prod] = version;\n\n ver = split(version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(ver); i++)\n ver[i] = int(ver[i]);\n\n fixed_version = '11.5.3';\n fix = split(fixed_version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(fix); i++)\n fix[i] = int(fix[i]);\n\n for (i=0; i<max_index(fix); i++)\n if ((ver[i] < fix[i]))\n {\n info +=\n '\\n Product : ' + prod +\n '\\n Installed version : ' + version +\n '\\n Fixed version : ' + fixed_version + '\\n';\n break;\n }\n else if (ver[i] > fix[i])\n break;\n}\n\nprod = 'Open XML File Format Converter for Mac';\nplist = \"/Applications/Open XML Converter.app/Contents/Info.plist\";\ncmd = 'cat \\'' + plist + '\\' | ' +\n 'grep -A 1 CFBundleShortVersionString | ' +\n 'tail -n 1 | ' +\n 'sed \\'s/.*string>\\\\(.*\\\\)<\\\\/string>.*/\\\\1/g\\'';\nversion = exec(cmd:cmd);\nif (version && version =~ \"^[0-9]+\\.\")\n{\n version = chomp(version);\n installs[prod] = version;\n\n ver = split(version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(ver); i++)\n ver[i] = int(ver[i]);\n\n fixed_version = '1.0.2';\n fix = split(fixed_version, sep:'.', keep:FALSE);\n for (i=0; i<max_index(fix); i++)\n fix[i] = int(fix[i]);\n\n for (i=0; i<max_index(fix); i++)\n if ((ver[i] < fix[i]))\n {\n info +=\n '\\n Product : ' + prod +\n '\\n Installed version : ' + version +\n '\\n Fixed version : ' + fixed_version + '\\n';\n break;\n }\n else if (ver[i] > fix[i])\n break;\n}\n\n\n# Report findings.\nif (info)\n{\n gs_opt = get_kb_item(\"global_settings/report_verbosity\");\n if (gs_opt && gs_opt != 'Quiet') security_hole(port:0, extra:info);\n else security_hole(0);\n\n exit(0);\n}\nelse\n{\n if (max_index(keys(installs)) == 0) exit(0, \"Office for Mac / Open XML File Format Converter is not installed.\");\n else\n {\n msg = 'The host has ';\n foreach prod (sort(keys(installs)))\n msg += prod + ' ' + installs[prod] + ' and ';\n msg = substr(msg, 0, strlen(msg)-1-strlen(' and '));\n\n msg += ' installed and thus is not affected.';\n\n exit(0, msg);\n }\n}\n", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2019-02-21T01:11:23", "bulletinFamily": "scanner", "description": "The remote host is running a version of Microsoft Word that may allow arbitrary code to be run on this host.\n\nTo succeed, the attacker would have to send a rogue file to a user of the remote computer and have him open it. Then a bug in the word record parsing handler would result in code execution.", "modified": "2018-11-15T00:00:00", "id": "SMB_NT_MS08-072.NASL", "href": "https://www.tenable.com/plugins/index.php?view=single&id=35071", "published": "2008-12-10T00:00:00", "title": "MS08-072: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (957173)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(35071);\n script_version(\"1.36\");\n script_cvs_date(\"Date: 2018/11/15 20:50:30\");\n\n script_cve_id(\n \"CVE-2008-4024\",\n \"CVE-2008-4025\",\n \"CVE-2008-4026\",\n \"CVE-2008-4027\",\n \"CVE-2008-4030\",\n \"CVE-2008-4028\",\n \"CVE-2008-4031\",\n \"CVE-2008-4837\"\n );\n script_bugtraq_id(\n 32579,\n 32580,\n 32581,\n 32583,\n 32584,\n 32585,\n 32594,\n 32642\n );\n script_xref(name:\"MSFT\", value:\"MS08-072\");\n script_xref(name:\"MSKB\", value:\"956328\");\n script_xref(name:\"MSKB\", value:\"956329\");\n script_xref(name:\"MSKB\", value:\"956357\");\n script_xref(name:\"MSKB\", value:\"956358\");\n script_xref(name:\"MSKB\", value:\"956366\");\n\n script_name(english:\"MS08-072: Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (957173)\");\n script_summary(english:\"Determines the version of WinWord.exe\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"Arbitrary code can be executed on the remote host through Microsoft\nWord.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host is running a version of Microsoft Word that may allow\narbitrary code to be run on this host.\n\nTo succeed, the attacker would have to send a rogue file to a user of\nthe remote computer and have him open it. Then a bug in the word record\nparsing handler would result in code execution.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2008/ms08-072\");\n script_set_attribute(attribute:\"solution\", value:\"Microsoft has released a set of patches for Word.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:H/RL:OF/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"exploited_by_malware\", value:\"true\");\n script_cwe_id(94, 399);\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2008/12/09\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2008/12/09\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2008/12/10\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:office\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:works\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:word\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:word_viewer\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/a:microsoft:office_compatibility_pack\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n\n script_copyright(english:\"This script is Copyright (C) 2008-2018 Tenable Network Security, Inc.\");\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_dependencies(\"smb_nt_ms02-031.nasl\", \"office_installed.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, 'Host/patch_management_checks');\n\n exit(0);\n}\n\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"misc_func.inc\");\ninclude(\"audit.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS08-072';\nkbs = make_list(\"956328\", \"956329\", \"956357\", \"956358\", \"956366\");\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nport = get_kb_item(\"SMB/transport\");\n\n\n\n#\n# Word\n#\nvuln = 0;\nlist = get_kb_list(\"SMB/Office/Word/*/ProductPath\");\nif (!isnull(list))\n{\n foreach item (keys(list))\n {\n v = item - 'SMB/Office/Word/' - '/ProductPath';\n if(ereg(pattern:\"^9\\..*\", string:v))\n {\n # Word 2000 - fixed in 9.0.0.8974\n office_sp = get_kb_item(\"SMB/Office/2000/SP\");\n if (!isnull(office_sp) && office_sp == 3)\n {\n sub = ereg_replace(pattern:\"^9\\.00?\\.00?\\.([0-9]*)$\", string:v, replace:\"\\1\");\n if(sub != v && int(sub) < 8974 ) {\n vuln++;\n kb = '956328';\n hotfix_add_report(bulletin:bulletin, kb:kb);\n }\n }\n }\n else if(ereg(pattern:\"^10\\..*\", string:v))\n {\n # Word XP - fixed in 10.0.6850.0\n office_sp = get_kb_item(\"SMB/Office/XP/SP\");\n if (!isnull(office_sp) && office_sp == 3)\n {\n middle = ereg_replace(pattern:\"^10\\.0\\.([0-9]*)\\.[0-9]*$\", string:v, replace:\"\\1\");\n if(middle != v && int(middle) < 6850 ) {\n vuln++;\n kb = '956329';\n hotfix_add_report(bulletin:bulletin, kb:kb);\n }\n }\n }\n else if(ereg(pattern:\"^11\\..*\", string:v))\n {\n # Word 2003 - fixed in 11.0.8237.0 :\n office_sp = get_kb_item(\"SMB/Office/2003/SP\");\n if (!isnull(office_sp) && office_sp == 3)\n {\n middle = ereg_replace(pattern:\"^11\\.0\\.([0-9]*)\\.[0-9]*$\", string:v, replace:\"\\1\");\n if(middle != v && int(middle) < 8237 ) {\n vuln++;\n kb = '956357';\n hotfix_add_report(bulletin:bulletin, kb:kb);\n }\n }\n }\n else if(ereg(pattern:\"^12\\..*\", string:v))\n {\n # Word 2007 - fixed in 12.0.6331.5000\n office_sp = get_kb_item(\"SMB/Office/2007/SP\");\n if (!isnull(office_sp) && (office_sp == 0 || office_sp == 1))\n {\n middle = ereg_replace(pattern:\"^12\\.0\\.([0-9]*)\\.[0-9]*$\", string:v, replace:\"\\1\");\n if(middle != v && int(middle) < 6331 ) {\n vuln++;\n kb = '956358';\n hotfix_add_report(bulletin:bulletin, kb:kb);\n }\n }\n }\n }\n}\n\n#\n# Word Viewer\n#\nlist = get_kb_list(\"SMB/Office/WordViewer/*/ProductPath\");\nif (!isnull(list))\n{\n foreach item (keys(list))\n {\n v = item - 'SMB/Office/WordViewer/' - '/ProductPath';\n if ( v && ereg(pattern:\"^11\\..*\", string:v))\n {\n # Word Viewer 2003 - fixed in 11.0.8241.0\n middle = ereg_replace(pattern:\"^11\\.0\\.([0-9]*)\\.[0-9]*$\", string:v, replace:\"\\1\");\n if(middle != v && int(middle) < 8241 ) {\n vuln++;\n kb = '956366';\n hotfix_add_report(bulletin:bulletin, kb:kb);\n }\n }\n }\n}\nif (vuln)\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\n exit(0);\n}\nelse audit(AUDIT_HOST_NOT, 'affected');\n", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}]}
