{"id": "SECURITYVULNS:DOC:24473", "bulletinFamily": "software", "title": "Microsoft Office Word HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903", "description": "Dear List,\r\n\r\nI'm writing on behalf of the Check Point Vulnerability Discovery Team to publish the following\r\nvulnerability.\r\n\r\nCheck Point Software Technologies - Vulnerability Discovery Team (VDT)\r\nhttp://www.checkpoint.com/defense/\r\n\r\nMicrosoft Office Word HTML Linked Objects Memory Corruption Vulnerability\r\nCVE-2010-1903 - MS10-056\r\n\r\nINTRODUCTION\r\n\r\nThere exists a vulnerability within the way Word handles html linked objects, which leads \r\nto attacker controlled memory write and code execution.\r\n\r\nThere is a poc.doc file that demonstrates the vulnerability and is available to interested\r\nparts.\r\n\r\nThis problem was confirmed in the following versions of Word and Windows, other versions \r\nmay be also affected.\r\n\r\nMicrosoft Office XP Service Pack 3 and older\r\nMicrosoft Office 2003 Service Pack 3 and older\r\n2007 Microsoft Office System Service Pack 2 and older\r\nMicrosoft Office 2004 for Mac\r\nMicrosoft Office 2008 for Mac\r\nOpen XML file format converter for Mac\r\nMicrosoft Office Word Viewer\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2\r\nMicrosoft Works 9\r\n\r\n\r\nCVSS Scoring System\r\n\r\nThe CVSS score is: 8.6\r\n Base Score: 10\r\n Temporal Score: 8.6\r\nWe used the following values to calculate the scores:\r\n Base score is: AV:N/AC:L/Au:N/C:C/I:C/A:C\r\n Temporal score is: E:POC/RL:U/RC:UR\r\n\r\n \r\nTRIGGERING THE PROBLEM\r\n\r\nThe problem is triggered by a PoC available only to interested parts which causes invalid memory write in\r\nall the referred versions.\r\n\r\n\r\nDETAILS\r\n\r\nOpening the attached poc.doc file and breaking in the following call, we see:\r\n\r\neax=00126c5c ebx=00126c40 ecx=00000000 edx=00000001 esi=00944001 edi=00000000\r\neip=3179fd74 esp=00126b9c ebp=00126bc0 iopl=0 nv up ei pl zr na pe nc\r\ncs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246\r\nwwlib!DllGetClassObject+0x7fe9e:\r\n3179fd74 e87bf9ffff call wwlib!DllGetClassObject+0x7f81e (3179f6f4)\r\n\r\nDisassembling the code:\r\n\r\n0:000> u\r\nwwlib!DllGetClassObject+0x7fe9e:\r\n3179fd74 e87bf9ffff call wwlib!DllGetClassObject+0x7f81e (3179f6f4)\r\n3179fd79 3bf7 cmp esi,edi\r\n3179fd7b 8b4310 mov eax,dword ptr [ebx+10h]\r\n3179fd7e 894508 mov dword ptr [ebp+8],eax\r\n3179fd81 7404 je wwlib!DllGetClassObject+0x7feb1 (3179fd87)\r\n3179fd83 66893c46 mov word ptr [esi+eax*2],di\r\n3179fd87 397b2c cmp dword ptr [ebx+2Ch],edi\r\n3179fd8a 740e je wwlib!DllGetClassObject+0x7fec4 (3179fd9a)\r\n\r\nThe faulting instruction is at address 3179fd83, where di and eax are NULL and esi a\r\nfixed value. The value eax is copied from the stack. The same with the di register.\r\n\r\nStepping into the first called function:\r\n\r\n0:000> u 3179f6f4\r\nwwlib!DllGetClassObject+0x7f81e:\r\n3179f6f4 55 push ebp\r\n3179f6f5 8bec mov ebp,esp\r\n3179f6f7 81ecb8010000 sub esp,offset <Unloaded_dui.DLL>+0x187 (000001b8)\r\n3179f6fd a170474831 mov eax,dword ptr [wwlib+0x244770 (31484770)]\r\n3179f702 33c5 xor eax,ebp\r\n3179f704 8945fc mov dword ptr [ebp-4],eax\r\n3179f707 838db0feffffff or dword ptr [ebp-150h],0FFFFFFFFh\r\n3179f70e 33c9 xor ecx,ecx\r\n\r\nThe stack trace information:\r\n\r\n0:000> k\r\nChildEBP RetAddr \r\nWARNING: Stack unwind information not available. Following frames may be wrong.\r\n00126bc0 315d18cb wwlib!DllGetClassObject+0x7fe9e\r\n00126d8c 315d02f7 wwlib!FMain+0x133a26\r\n00126e18 315cf42f wwlib!FMain+0x132452\r\n00127430 315cefc0 wwlib!FMain+0x13158a\r\n0012763c 315ce9ba wwlib!FMain+0x13111b\r\n001276d4 6bdd1d83 wwlib!FMain+0x130b15\r\n00127784 6bdd24c8 MSPTLS!LssbFIsSublineEmpty+0x22cb\r\n00127804 6bddf8e0 MSPTLS!LssbFIsSublineEmpty+0x2a10\r\n00127868 6bddff5d MSPTLS!LssbFIsSublineEmpty+0xfe28\r\n00127898 6bddf1ef MSPTLS!LssbFIsSublineEmpty+0x104a5\r\n00127a9c 6bdc4b85 MSPTLS!LssbFIsSublineEmpty+0xf737\r\n00127ad0 318e1917 MSPTLS!LsCreateLine+0x23\r\n00127b44 3181c5f8 wwlib!DllGetClassObject+0x1c1a41\r\n00127bac 31549412 wwlib!DllGetClassObject+0xfc722\r\n00127c9c 6be51b06 wwlib!FMain+0xab56d\r\n00127d3c 6be5c63a MSPTLS!FsDestroyMemory+0x1ee39\r\n00127eb4 6be5c92b MSPTLS!FsDestroyMemory+0x2996d\r\n00127f00 6be36d4d MSPTLS!FsDestroyMemory+0x29c5e\r\n00127f6c 6be37f7b MSPTLS!FsDestroyMemory+0x4080\r\n00128078 6be4e8ca MSPTLS!FsDestroyMemory+0x52ae\r\n\r\n!exploitable output:\r\nExploitability Classification: EXPLOITABLE\r\nRecommended Bug Title: Exploitable - User Mode Write AV starting at\r\nwwlib!DllGetClassObject+0x000000000007fead (Hash=0x43317a27.0x44020844)\r\nUser mode write access violations that are not near NULL are exploitable.\r\n\r\nThis vulnerability can be remotely triggered if an user choose to open a .doc while using IE or any other\r\nbrowser (in\r\nIE it will spawn a winword.exe process inside the browser, but the process remains as a new one).\r\n\r\n\r\nCREDITS\r\n\r\nThis vulnerability was discovered and researched by Rodrigo Rubira Branco from \r\nCheck Point Vulnerability Discovery Team (VDT).\r\n\r\n\r\n\r\nBest Regards,\r\n \r\nRodrigo.\r\n \r\n--\r\nRodrigo Rubira Branco\r\nSenior Security Researcher\r\nVulnerability Discovery Team (VDT)\r\nCheck Point Software Technologies", "published": "2010-08-11T00:00:00", "modified": "2010-08-11T00:00:00", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:24473", "reporter": "Securityvulns", "references": [], "cvelist": ["CVE-2010-1903"], "type": "securityvulns", "lastseen": "2018-08-31T11:10:36", "edition": 1, "viewCount": 5, "enchantments": {"score": {"value": 7.7, "vector": "NONE", "modified": "2018-08-31T11:10:36", "rev": 2}, "dependencies": {"references": [{"type": "cve", "idList": ["CVE-2010-1903"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:24461", "SECURITYVULNS:VULN:11055", "SECURITYVULNS:DOC:24502"]}, {"type": "zdi", "idList": ["ZDI-10-151"]}, {"type": "openvas", "idList": ["OPENVAS:902228", "OPENVAS:1361412562310902228"]}, {"type": "nessus", "idList": ["SMB_NT_MS10-056.NASL"]}], "modified": "2018-08-31T11:10:36", "rev": 2}, "vulnersScore": 7.7}, "affectedSoftware": []}

{"cve": [{"lastseen": "2020-10-03T11:57:25", "description": "Microsoft Office Word 2002 SP3 and 2003 SP3, and Office Word Viewer, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a malformed record in a Word file, aka \"Word HTML Linked Objects Memory Corruption Vulnerability.\"", "edition": 3, "cvss3": {}, "published": "2010-08-11T18:47:00", "title": "CVE-2010-1903", "type": "cve", "cwe": ["CWE-94"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 8.6, "obtainAllPrivilege": true, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 9.3, "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2010-1903"], "modified": "2018-10-12T21:57:00", "cpe": ["cpe:/a:microsoft:office_word_viewer:*", "cpe:/a:microsoft:word:2003", "cpe:/a:microsoft:word:2002"], "id": "CVE-2010-1903", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1903", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:a:microsoft:office_word_viewer:*:*:*:*:*:*:*:*", "cpe:2.3:a:microsoft:word:2002:sp3:*:*:*:*:*:*", "cpe:2.3:a:microsoft:word:2003:sp3:*:*:*:*:*:*"]}], "zdi": [{"lastseen": "2020-06-22T11:40:41", "bulletinFamily": "info", "cvelist": ["CVE-2010-1903"], "edition": 3, "description": "This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Microsoft Word. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the code responsible for parsing the plcffldMom structure within .doc files. By crafting malicious values within this structure an attacker can force the program to make faulty heap memory allocations. This can be leveraged to execute remote code under the context of the user running the application.", "modified": "2010-06-22T00:00:00", "published": "2010-08-11T00:00:00", "href": "https://www.zerodayinitiative.com/advisories/ZDI-10-151/", "id": "ZDI-10-151", "title": "Microsoft Office Word 2007 plcffldMom Parsing Remote Code Execution Vulnerability", "type": "zdi", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:36", "bulletinFamily": "software", "cvelist": ["CVE-2010-1903"], "description": "ZDI-10-151: Microsoft Office Word 2007 plcffldMom Parsing Remote Code Execution Vulnerability\r\nhttp://www.zerodayinitiative.com/advisories/ZDI-10-151\r\nAugust 11, 2010\r\n\r\n-- CVE ID:\r\n CVE-2010-1903\r\n\r\n-- CVSS:\r\n10, &#40;AV:N/AC:L/Au:N/C:C/I:C/A:C&#41;\r\n\r\n-- Affected Vendors:\r\nMicrosoft\r\n\r\n-- Affected Products:\r\nMicrosoft Office Word\r\n\r\n-- TippingPoint&#40;TM&#41; IPS Customer Protection:\r\nTippingPoint IPS customers have been protected against this\r\nvulnerability by Digital Vaccine protection filter ID 10129. \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 Word. User interaction is required\r\nto exploit this vulnerability in that the target must visit a malicious\r\npage or open a malicious file.\r\n\r\nThe specific flaw exists within the code responsible for parsing the\r\nplcffldMom structure within .doc files. By crafting malicious values\r\nwithin this structure an attacker can force the program to make faulty\r\nheap memory allocations. This can be leveraged to execute remote code\r\nunder the context of the user running the application.\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/ms10-056.mspx\r\n\r\n-- Disclosure Timeline:\r\n2010-06-02 - Vulnerability reported to vendor\r\n2010-08-11 - Coordinated public release of advisory\r\n\r\n-- Credit:\r\nThis vulnerability was discovered by:\r\n * Anonymous\r\n\r\n-- About the Zero Day Initiative &#40;ZDI&#41;:\r\nEstablished by TippingPoint, The Zero Day Initiative &#40;ZDI&#41; 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 &#40;including competitors&#41; 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\nFollow the ZDI on Twitter:\r\n\r\n http://twitter.com/thezdi", "edition": 1, "modified": "2010-08-14T00:00:00", "published": "2010-08-14T00:00:00", "id": "SECURITYVULNS:DOC:24502", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:24502", "title": "ZDI-10-151: Microsoft Office Word 2007 plcffldMom Parsing Remote Code Execution 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:36", "bulletinFamily": "software", "cvelist": ["CVE-2010-1901", "CVE-2010-1903", "CVE-2010-1902", "CVE-2010-1900"], "description": "Microsoft Security Bulletin MS10-056 - Critical\r\nVulnerabilities in Microsoft Office Word Could Allow Remote Code Execution &#40;2269638&#41;\r\nPublished: August 10, 2010\r\n\r\nVersion: 1.0\r\nGeneral Information\r\nExecutive Summary\r\n\r\nThis security update resolves four privately reported vulnerabilities in Microsoft Office. The most severe vulnerabilities could allow remote code execution if a user opens or previews a specially crafted RTF e-mail message. An attacker who successfully exploited any of these vulnerabilities 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\r\nThis security update is rated Critical for all supported editions of Microsoft Office Word 2007. This security update is also rated Important for all supported editions of Microsoft Office Word 2002, Microsoft Office Word 2003, Microsoft Office 2004 for Mac, and Microsoft Office 2008 for Mac; Open XML File Format Converter for Mac; Works 9; and all supported versions of Microsoft Office Word Viewer and Microsoft Office Compatibility Pack. For more information, see the subsection, Affected and Non-Affected Software, in this section.\r\n\r\nThe update addresses the vulnerabilities by modifying the way that Microsoft Office Word opens specially crafted Word files and by modifying the way that Word handles certain properties of rich text data. For more information about the vulnerability, see the Frequently Asked Questions &#40;FAQ&#41; 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. None\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 XP Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Word 2002 Service Pack 3\r\n&#40;KB2251389&#41;\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS09-068\r\n\r\nMicrosoft Office 2003 Service Pack 3\r\n\t\r\n\r\nMicrosoft Office Word 2003 Service Pack 3\r\n&#40;KB2251399&#41;\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nMS10-036\r\n\r\n2007 Microsoft Office System Service Pack 2\r\n\t\r\n\r\nMicrosoft Office Word 2007 Service Pack 2\r\n&#40;KB2251419&#41;\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nMS10-036\r\nMicrosoft Office for Mac\t \t \t \t \r\n\r\nMicrosoft Office 2004 for Mac\r\n&#40;KB2284171&#41;\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\nMS09-068\r\n\r\nMicrosoft Office 2008 for Mac\r\n&#40;KB2284162&#41;\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\nMS09-068\r\n\r\nOpen XML File Format Converter for Mac\r\n&#40;KB2284179&#41;\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\nMS09-068\r\nOther Software\t \t \t \t \r\n\r\nMicrosoft Office Word Viewer\r\n&#40;KB2251437&#41;\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\nMS09-068\r\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2\r\n&#40;KB2277947&#41;\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\nMS09-027\r\n\r\nMicrosoft Works 9\r\n&#40;KB2092914&#41;\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\nNone\r\n\r\nNon-Affected Software\r\nOffice and Other Software\r\n\r\nMicrosoft Office Word 2010 &#40;32-bit editions&#41;\r\n\r\nMicrosoft Office Word 2010 &#40;64-bit editions&#41;\r\nTop of sectionTop of section\r\n\t\r\nFrequently Asked Questions &#40;FAQ&#41; Related to This Security Update\r\n\r\nHow is Microsoft Office Outlook affected by these vulnerabilities? \r\nOutlook is not directly affected because the vulnerabilities exist in Microsoft Office Word. However, if Word is the selected e-mail reader, which is the default case in Microsoft Office Outlook 2007, then an attacker could leverage Outlook for the e-mail attack vector by sending a specially crafted RTF e-mail message to the target user.\r\n\r\nWhere are the file information details? \r\nRefer to the reference tables in the Security Update Deployment section for the location of the file information details.\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\nWhat is the Microsoft Office Word Viewer? \r\nThe Microsoft Office Word Viewer is a replacement for Word Viewer 2003 and all previous Word Viewer versions. With Word Viewer, you can view, print, and copy Word documents, even if you do not have Word installed. For more details about currently supported Office viewers, see Supported versions of the Office viewers.\r\n\r\nHow are Office standalone programs affected by the vulnerability? \r\nAn Office standalone program is affected with the same severity rating as the corresponding component in an Office Suite. For example, a standalone installation of Microsoft Office Word is affected with the same severity rating as an installation of Microsoft Office Word that was delivered with an Office Suite.\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 component discussed in this bulletin was delivered with the version of the Office Suite installed on your system, 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 were delivered with the particular Office Suite and to offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is delivered with their version of the Office Suite, will not increase the security risk of that system. On the other hand, users who do choose to install the update will not have a negative impact on the security or performance of a system.\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 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. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.\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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.\r\n\r\nCustomers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ.\r\nTop of sectionTop of section\r\nVulnerability Information\r\n\t\r\nSeverity Ratings and Vulnerability Identifiers\r\n\r\nThe following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin&#39;s release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the August bulletin summary. For more information, see Microsoft Exploitability Index.\r\nVulnerability Severity Rating and Maximum Security Impact by Affected Software\r\nAffected Software\tWord Record Parsing Vulnerability - CVE-2010-1900 \tWord RTF Parsing Engine Memory Corruption Vulnerability - CVE-2010-1901\tWord RTF Parsing Buffer Overflow Vulnerability - CVE-2010-1902\tWord HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903\tAggregate Severity Rating\r\nMicrosoft Office Suites and Components\t \t \t \t \t \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\n\r\nMicrosoft Office Word 2003 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\n\r\nMicrosoft Office Word 2007 Service Pack 2\r\n\t\r\n\r\nImportant \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\nNot applicable\r\n\t\r\n\r\nCritical\r\nMicrosoft Office for Mac\t \t \t \t \t \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\nNot applicable\r\n\t\r\n\r\nImportant\r\n\r\nMicrosoft Office 2008 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\nNot applicable\r\n\t\r\n\r\nImportant\r\n\r\nOpen XML File Format Converter 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\nNot applicable\r\n\t\r\n\r\nImportant\r\nOther Software\t \t \t \t \t \r\n\r\nMicrosoft Office Word Viewer\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\n\r\nMicrosoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2\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\nNot applicable\r\n\t\r\n\r\nImportant\r\n\r\nMicrosoft Works 9\r\n\t\r\n\r\nImportant \r\nRemote Code Execution\r\n\t\r\n\r\nNot applicable\r\n\t\r\n\r\nNot applicable\r\n\t\r\n\r\nNot applicable\r\n\t\r\n\r\nImportant\r\nTop of sectionTop of section\r\n\t\r\nWord Record Parsing Vulnerability - CVE-2010-1900\r\n\r\nA remote code execution vulnerability exists in the way that Microsoft Office Word handles malformed records inside a specially crafted Word file. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-1900.\r\n\t\r\nMitigating Factors for Word Record Parsing Vulnerability - CVE-2010-1900\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\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\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 convince them to open the specially crafted Word file.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word Record Parsing Vulnerability - CVE-2010-1900\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\nUse Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations\r\n\r\nThe following registry scripts can be used to set the File Block policy.\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\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.\r\n\r\nImpact of workaround. Users who have configured the File Block policy and have not configured a special &quot;exempt directory&quot; as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.\r\n\r\nHow to undo the workaround.\r\n\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nUse the Microsoft Office Isolated Conversion Environment &#40;MOICE&#41; when opening files from unknown or untrusted sources\r\n\r\nThe Microsoft Office Isolated Conversion Environment &#40;MOICE&#41; helps 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 also 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\nEnable MOICE\r\n\r\nNote See Microsoft Knowledge Base Article 935865 to use the automated Microsoft Fix it solution to enable or disable this workaround.\r\n\r\nTo manually enable MOICE, run the commands as specified in the following table. Running the commands will associate the Office application extensions with MOICE.\r\nCommand to enable MOICE to be the registered handler\r\n\r\nFor Word, run the following command from a command prompt:\r\nASSOC .doc=oice.word.document\r\n\r\nFor Excel, run the following commands from a command prompt:\r\nASSOC .XLS=oice.excel.sheet\r\nASSOC .XLT=oice.excel.template\r\nASSOC .XLA=oice.excel.addin\r\n\r\nFor PowerPoint, run the following commands from a command prompt:\r\nASSOC .PPT=oice.powerpoint.show\r\nASSOC .POT=oice.powerpoint.template\r\nASSOC .PPS=oice.powerpoint.slideshow\r\n\r\nNote On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands 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\n\r\nHow to undo the workaround. Run the commands to disable MOICE as specified in the table below.\r\nCommand to disable MOICE as the registered handler\r\n\r\nFor Word, run the following command from a command prompt:\r\nASSOC .doc=Word.Document.8\r\n\r\nFor Excel, run the following commands from a command prompt:\r\nASSOC .xls=Excel.Sheet.8\r\nASSOC .xlt=Excel.Template\r\nASSOC .xla=Excel.Addin\r\n\r\nFor PowerPoint, run the following commands from a command prompt:\r\nASSOC .ppt=PowerPoint.Show.8\r\nASSOC .PPS=oice.powerpoint.slideshow\r\nASSOC .pps=PowerPoint.SlideShow.8\r\n\r\nNote On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands from an elevated command prompt.\r\n\u2022\t\r\n\r\nDo not open Word files that you receive from untrusted sources or that you receive unexpectedly from trusted sources\r\n\r\nDo not open Word 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 Record Parsing Vulnerability - CVE-2010-1900\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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability? \r\nWhen Microsoft Office Word 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. 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. 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 document 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 a 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&#39;s site, and then convince them to open the specially crafted Word file.\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\nThis update addresses the vulnerability by modifying the way that Microsoft Office Word opens specially crafted Word 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 coordinated vulnerability disclosure.\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 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 Parsing Engine Memory Corruption Vulnerability - CVE-2010-1901\r\n\r\nA remote code execution vulnerability exists in the way that Microsoft Office Word parses rich text data. An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-1901.\r\n\t\r\nMitigating Factors for Word RTF Parsing Engine Memory Corruption Vulnerability - CVE-2010-1901\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\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Parsing Engine Memory Corruption Vulnerability - CVE-2010-1901\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\nRead e-mails in plain text\r\n\r\nTo help protect yourself from the e-mail attack vector, read e-mail messages in plain text format.\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 in plain text only those e-mail messages that are not digitally signed or e-mail messages that are not encrypted.\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 &#40;custom code solutions&#41; may behave unexpectedly.\r\n\u2022\t\r\n\r\nUse Microsoft Office File Block policy to block the opening of RTF documents from unknown or untrusted sources and locations\r\n\r\nThe following registry scripts can be used to set the File Block policy.\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\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.\r\n\r\nImpact of workaround. Users who have configured the File Block policy and have not configured a special &quot;exempt directory&quot; as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.\r\n\r\nHow to undo the workaround.\r\n\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000000\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Parsing Engine Memory Corruption Vulnerability - CVE-2010-1901\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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability? \r\nMicrosoft Office Word does not perform sufficient data validation when handling rich text data. When Word opens and parses a specially crafted RTF e-mail message or file, it may corrupt 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 cause arbitrary code to run with the privileges of the user who opens a specially crafted RTF file or previews or opens a specially crafted RTF e-mail message. If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with 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\nHow could an attacker exploit the vulnerability? \r\nIn an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted RTF file as an attachment or in the contents of an e-mail message and convincing the user to view the specially crafted RTF e-mail message in Outlook when using Word as the e-mail viewer.\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a 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 persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s site.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nWorkstations and terminal servers that have Microsoft Office Word installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.\r\n\r\nWhat does the update do? \r\nThe update addresses the vulnerability by modifying the way that Word handles certain properties of rich text data.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.\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 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 Parsing Buffer Overflow Vulnerability - CVE-2010-1902\r\n\r\nA remote code execution vulnerability exists in the way that Microsoft Office Word parses certain rich text data. An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-1902.\r\n\t\r\nMitigating Factors for Word RTF Parsing Buffer Overflow Vulnerability - CVE-2010-1902\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\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word RTF Parsing Buffer Overflow Vulnerability - CVE-2010-1902\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\nRead e-mails in plain text\r\n\r\nTo help protect yourself from the e-mail attack vector, read e-mail messages in plain text format.\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 in plain text only those e-mail messages that are not digitally signed or e-mail messages that are not encrypted.\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 &#40;custom code solutions&#41; may behave unexpectedly.\r\n\u2022\t\r\n\r\nUse Microsoft Office File Block policy to block the opening of RTF documents from unknown or untrusted sources and locations\r\n\r\nThe following registry scripts can be used to set the File Block policy.\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\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.\r\n\r\nImpact of workaround. Users who have configured the File Block policy and have not configured a special &quot;exempt directory&quot; as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.\r\n\r\nHow to undo the workaround.\r\n\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;RtfFiles&quot;=dword:00000000\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Word RTF Parsing Buffer Overflow Vulnerability - CVE-2010-1902\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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability? \r\nMicrosoft Office Word does not perform sufficient data validation when handling rich text data. When Word opens and parses a specially crafted e-mail message or file, it may corrupt 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 cause arbitrary code to run with the privileges of the user who opens a specially crafted RTF file or previews or opens a specially crafted RTF e-mail message. If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with 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\nHow could an attacker exploit the vulnerability? \r\nIn an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted RTF file as an attachment or in the contents of an e-mail message and convincing the user to view the specially crafted RTF e-mail message in Outlook when using Word as the e-mail viewer.\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a 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 persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s site.\r\n\r\nWhat systems are primarily at risk from the vulnerability? \r\nWorkstations and terminal servers that have Microsoft Office Word installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.\r\n\r\nWhat does the update do? \r\nThe update addresses the vulnerability by modifying the way that Word handles certain properties of rich text data.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed? \r\nNo. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.\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 when this security bulletin was originally issued.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWord HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903\r\n\r\nA remote code execution vulnerability exists in the way that Microsoft Office Word handles a specially crafted Word file that includes a malformed record. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.\r\n\r\nTo view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-1903.\r\n\t\r\nMitigating Factors for Word HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903\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\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\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 convince them to open the specially crafted Word file.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Word HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903\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\nUse Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations\r\n\r\nThe following registry scripts can be used to set the File Block policy.\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\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000001\r\n\r\nNote In order to use &#39;FileOpenBlock&#39; with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.\r\n\r\nImpact of workaround. Users who have configured the File Block policy and have not configured a special &quot;exempt directory&quot; as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.\r\n\r\nHow to undo the workaround.\r\n\u2022\t\r\n\r\nFor Office 2003\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Microsoft&#92;Office&#92;11.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nFor 2007 Office system\r\n\r\nWindows Registry Editor Version 5.00\r\n[HKEY_CURRENT_USER&#92;Software&#92;Policies&#92;Microsoft&#92;Office&#92;12.0&#92;Word&#92;Security&#92;FileOpenBlock]\r\n&quot;BinaryFiles&quot;=dword:00000000\r\n\u2022\t\r\n\r\nUse the Microsoft Office Isolated Conversion Environment &#40;MOICE&#41; when opening files from unknown or untrusted sources\r\n\r\nThe Microsoft Office Isolated Conversion Environment &#40;MOICE&#41; helps 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 also 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\nEnable MOICE\r\n\r\nNote See Microsoft Knowledge Base Article 935865 to use the automated Microsoft Fix it solution to enable or disable this workaround.\r\n\r\nTo manually enable MOICE, run the commands as specified in the following table. Running the commands will associate the Office application extensions with MOICE.\r\nCommand to enable MOICE to be the registered handler\r\n\r\nFor Word, run the following command from a command prompt:\r\nASSOC .doc=oice.word.document\r\n\r\nFor Excel, run the following commands from a command prompt:\r\nASSOC .XLS=oice.excel.sheet\r\nASSOC .XLT=oice.excel.template\r\nASSOC .XLA=oice.excel.addin\r\n\r\nFor PowerPoint, run the following commands from a command prompt:\r\nASSOC .PPT=oice.powerpoint.show\r\nASSOC .POT=oice.powerpoint.template\r\nASSOC .PPS=oice.powerpoint.slideshow\r\n\r\nNote On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands 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\n\r\nHow to undo the workaround. Run the commands to disable MOICE as specified in the table below.\r\nCommand to disable MOICE as the registered handler\r\n\r\nFor Word, run the following command from a command prompt:\r\nASSOC .doc=Word.Document.8\r\n\r\nFor Excel, run the following commands from a command prompt:\r\nASSOC .xls=Excel.Sheet.8\r\nASSOC .xlt=Excel.Template\r\nASSOC .xla=Excel.Addin\r\n\r\nFor PowerPoint, run the following commands from a command prompt:\r\nASSOC .ppt=PowerPoint.Show.8\r\nASSOC .PPS=oice.powerpoint.slideshow\r\nASSOC .pps=PowerPoint.SlideShow.8\r\n\r\nNote On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands from an elevated command prompt.\r\n\u2022\t\r\n\r\nDo not open Word files that you receive from untrusted sources or that you receive unexpectedly from trusted sources\r\n\r\nDo not open Word 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 HTML Linked Objects Memory Corruption Vulnerability - CVE-2010-1903\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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWhat causes the vulnerability? \r\nWhen Microsoft Office Word 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. 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. 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 document 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 Office 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&#39;s site, and then convince them to open the specially crafted Word file.\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\nThis update addresses the vulnerability by modifying the way that Microsoft Office Word opens specially crafted Word 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 coordinated vulnerability disclosure.\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 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\nL.W.Z of team509, working with TippingPoint&#39;s Zero Day Initiative, for reporting the Word Record Parsing Vulnerability &#40;CVE-2010-1900&#41;\r\n\u2022\t\r\n\r\nWushi of team509, working with VeriSign iDefense Labs, for reporting the Word RTF Parsing Engine Memory Corruption Vulnerability &#40;CVE-2010-1901&#41;\r\n\u2022\t\r\n\r\nteam509, working with VeriSign iDefense Labs, for reporting the Word RTF Parsing Buffer Overflow Vulnerability &#40;CVE-2010-1902&#41;\r\n\u2022\t\r\n\r\nRodrigo Rubira Branco of the Check Point IPS Research Team for reporting the Word HTML Linked Objects Memory Corruption &#40;CVE-2010-1903&#41;\r\nTop of sectionTop of section\r\nMicrosoft Active Protections Program &#40;MAPP&#41;\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 &#40;MAPP&#41; Partners.\r\n\r\nSupport\r\n\u2022\t\r\n\r\nCustomers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.\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 &quot;as is&quot; 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\n\r\nRevisions\r\n\u2022\t\r\n\r\nV1.0 &#40;August 10, 2010&#41;: Bulletin published.", "edition": 1, "modified": "2010-08-11T00:00:00", "published": "2010-08-11T00:00:00", "id": "SECURITYVULNS:DOC:24461", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:24461", "title": "Microsoft Security Bulletin MS10-056 - Critical Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution &#40;2269638&#41;", "type": "securityvulns", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2018-08-31T11:09:38", "bulletinFamily": "software", "cvelist": ["CVE-2010-2562", "CVE-2010-1901", "CVE-2010-1903", "CVE-2010-1902", "CVE-2010-1900"], "description": "Multiple memory corruptions on different data type parsing in Word and Excel.", "edition": 1, "modified": "2010-08-16T00:00:00", "published": "2010-08-16T00:00:00", "id": "SECURITYVULNS:VULN:11055", "href": "https://vulners.com/securityvulns/SECURITYVULNS:VULN:11055", "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": "2020-06-10T20:03:01", "bulletinFamily": "scanner", "cvelist": ["CVE-2010-1901", "CVE-2010-1903", "CVE-2010-1902", "CVE-2010-1900"], "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS10-056.", "modified": "2020-06-09T00:00:00", "published": "2010-08-11T00:00:00", "id": "OPENVAS:1361412562310902228", "href": "http://plugins.openvas.org/nasl.php?oid=1361412562310902228", "type": "openvas", "title": "Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n#\n# Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)\n#\n# Authors:\n# Antu Sanadi <santu@secpod.com>\n#\n# Copyright:\n# Copyright (C) 2010 SecPod, http://www.secpod.com\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.902228\");\n script_version(\"2020-06-09T10:15:40+0000\");\n script_tag(name:\"last_modification\", value:\"2020-06-09 10:15:40 +0000 (Tue, 09 Jun 2020)\");\n script_tag(name:\"creation_date\", value:\"2010-08-11 15:08:29 +0200 (Wed, 11 Aug 2010)\");\n script_cve_id(\"CVE-2010-1900\", \"CVE-2010-1901\", \"CVE-2010-1902\", \"CVE-2010-1903\");\n script_bugtraq_id(42133, 42132);\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_name(\"Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)\");\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2010 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/Prdts/Installed\");\n\n script_xref(name:\"URL\", value:\"http://support.microsoft.com/kb/2251389\");\n script_xref(name:\"URL\", value:\"http://support.microsoft.com/kb/2251399\");\n script_xref(name:\"URL\", value:\"http://support.microsoft.com/kb/2251437\");\n script_xref(name:\"URL\", value:\"http://support.microsoft.com/kb/2251419\");\n script_xref(name:\"URL\", value:\"http://www.vupen.com/english/advisories/2010/2053\");\n script_xref(name:\"URL\", value:\"https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-056\");\n\n script_tag(name:\"impact\", value:\"Successful exploitation could allow attackers to execute arbitrary code by\n tricking a user into opening a specially crafted Excel document.\");\n\n script_tag(name:\"affected\", value:\"- Microsoft Office Word Viewer\n\n - Microsoft Office Word 2002 Service Pack 3\n\n - Microsoft Office Word 2003 Service Pack 3\n\n - Microsoft Office Word 2007 Service Pack 2\n\n - Microsoft Office Compatibility Pack for Word, Excel and PowerPoint 2007 File Formats Service Pack 2\");\n\n script_tag(name:\"insight\", value:\"The issues are caused by buffer overflow and memory corruption errors when\n processing malformed data and records within Word and 'RTF' documents, which\n could be exploited by attackers to crash an affected application or execute\n arbitrary code.\");\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 MS10-056.\");\n\n script_tag(name:\"qod_type\", value:\"registry\");\n script_tag(name:\"solution_type\", value:\"VendorFix\");\n\n exit(0);\n}\n\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\n\nif(hotfix_check_sp(xp:4, win2003:3) <= 0){\n exit(0);\n}\n\nwinwordVer= get_kb_item(\"SMB/Office/Word/Version\");\nif(winwordVer =~ \"^1[0-2]\\.\")\n{\n if(version_in_range(version:winwordVer, test_version:\"10.0\", test_version2:\"10.0.6863.0\") ||\n version_in_range(version:winwordVer, test_version:\"11.0\", test_version2:\"11.0.8325.0\") ||\n version_in_range(version:winwordVer, test_version:\"12.0\", test_version2:\"12.0.6541.4999\"))\n {\n report = report_fixed_ver(installed_version:winwordVer, vulnerable_range:\"10.0 - 10.0.6863.0, 11.0 - 11.0.8325.0, 12.0 - 12.0.6541.4999\");\n security_message(port:0, data:report);\n exit(0);\n }\n}\n\nwordcnvVer = get_kb_item(\"SMB/Office/WordCnv/Version\");\nif(wordcnvVer =~ \"^12\\.\")\n{\n if(version_in_range(version:wordcnvVer, test_version:\"12.0\", test_version2:\"12.0.6539.4999\"))\n {\n report = report_fixed_ver(installed_version:wordcnvVer, vulnerable_range:\"12.0 - 12.0.6539.4999\");\n security_message(port:0, data:report);\n exit(0);\n }\n}\n\nwordviewVer = get_kb_item(\"SMB/Office/WordView/Version\");\nif(wordviewVer =~ \"^11\\.\")\n{\n if(version_in_range(version:wordviewVer, test_version:\"11.0\", test_version2:\"11.0.8325.0\")){\n report = report_fixed_ver(installed_version:wordviewVer, vulnerable_range:\"11.0 - 11.0.8325.0\");\n security_message(port:0, data:report);\n }\n}\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}, {"lastseen": "2017-07-20T08:48:58", "bulletinFamily": "scanner", "cvelist": ["CVE-2010-1901", "CVE-2010-1903", "CVE-2010-1902", "CVE-2010-1900"], "description": "This host is missing a critical security update according to\n Microsoft Bulletin MS10-056.", "modified": "2017-07-05T00:00:00", "published": "2010-08-11T00:00:00", "id": "OPENVAS:902228", "href": "http://plugins.openvas.org/nasl.php?oid=902228", "type": "openvas", "title": "Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)", "sourceData": "###############################################################################\n# OpenVAS Vulnerability Test\n# $Id: secpod_ms10-056.nasl 10593 2010-08-11 12:12:09Z aug$\n#\n# Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)\n#\n# Authors:\n# Antu Sanadi <santu@secpod.com>\n#\n# Copyright:\n# Copyright (c) 2010 SecPod, http://www.secpod.com\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 allow attackers to execute arbitrary code by\n tricking a user into opening a specially crafted Excel document.\n Impact Level: System/Application\";\ntag_affected = \"Microsoft Office Word Viewer\n Microsoft Office Word 2002 Service Pack 3\n Microsoft Office Word 2003 Service Pack 3\n Microsoft Office Word 2007 Service Pack 2\n Microsoft Office Compatibility Pack for Word,\n Excel, and PowerPoint 2007 File Formats Service Pack 2\";\ntag_insight = \"The issues are caused by buffer overflow and memory corruption errors when\n processing malformed data and records within Word and 'RTF' documents, which\n could be exploited by attackers to crash an affected application or execute\n arbitrary code.\";\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/ms10-056.mspx\";\ntag_summary = \"This host is missing a critical security update according to\n Microsoft Bulletin MS10-056.\";\n\nif(description)\n{\n script_id(902228);\n script_version(\"$Revision: 6533 $\");\n script_tag(name:\"last_modification\", value:\"$Date: 2017-07-05 10:41:34 +0200 (Wed, 05 Jul 2017) $\");\n script_tag(name:\"creation_date\", value:\"2010-08-11 15:08:29 +0200 (Wed, 11 Aug 2010)\");\n script_cve_id(\"CVE-2010-1900\",\"CVE-2010-1901\", \"CVE-2010-1902\", \"CVE-2010-1903\");\n script_bugtraq_id(42133, 42132);\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_name(\"Microsoft Office Word Remote Code Execution Vulnerabilities (2269638)\");\n script_xref(name : \"URL\" , value : \"http://support.microsoft.com/kb/2251389\");\n script_xref(name : \"URL\" , value : \"http://support.microsoft.com/kb/2251399\");\n script_xref(name : \"URL\" , value : \"http://support.microsoft.com/kb/2251437\");\n script_xref(name : \"URL\" , value : \"http://support.microsoft.com/kb/2251419\");\n script_xref(name : \"URL\" , value : \"http://www.vupen.com/english/advisories/2010/2053\");\n script_xref(name : \"URL\" , value : \"http://www.microsoft.com/technet/security/bulletin/ms10-056.mspx\");\n\n script_category(ACT_GATHER_INFO);\n script_copyright(\"Copyright (C) 2010 SecPod\");\n script_family(\"Windows : Microsoft Bulletins\");\n script_dependencies(\"secpod_office_products_version_900032.nasl\",\n \"secpod_ms_office_detection_900025.nasl\");\n script_mandatory_keys(\"MS/Office/Prdts/Installed\");\n script_require_ports(139, 445);\n script_mandatory_keys(\"SMB/WindowsVersion\");\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\n\ninclude(\"secpod_reg.inc\");\ninclude(\"version_func.inc\");\n\nif(hotfix_check_sp(xp:4, win2003:3) <= 0){\n exit(0);\n}\n\n## Microsoft Office Word 2002/2003/2007\nwinwordVer= get_kb_item(\"SMB/Office/Word/Version\");\nif(!isnull(winwordVer))\n{\n # Grep for version Winword.exe 10 < 10.0.6864.0 , 12 < 12.0.6541.5000\t, 11< 11.0.8326.0\t\n if(version_in_range(version:winwordVer, test_version:\"10.0\", test_version2:\"10.0.6863.0\") ||\n version_in_range(version:winwordVer, test_version:\"11.0\", test_version2:\"11.0.8325.0\") ||\n version_in_range(version:winwordVer, test_version:\"12.0\", test_version2:\"12.0.6541.4999\"))\n {\n security_message(0);\n exit(0);\n }\n}\n\n# Check for Office Word Version 2007 with compatiability pack\nwordcnvVer = get_kb_item(\"SMB/Office/WordCnv/Version\");\nif(!isnull(wordcnvVer))\n{\n # Check for Word Converter 2007 version 12.0 < 12.0.6539.5000\t\n if(version_in_range(version:wordcnvVer, test_version:\"12.0\", test_version2:\"12.0.6539.4999\"))\n {\n security_message(0);\n exit(0);\n }\n}\n\n# Check for Word Viewer 11.0 < 11.0.8326.0\nwordviewVer = get_kb_item(\"SMB/Office/WordView/Version\");\nif(wordviewVer != NULL)\n{\n if(version_in_range(version:wordviewVer, test_version:\"11.0\", test_version2:\"11.0.8325.0\")){\n security_message(0);\n }\n}\n", "cvss": {"score": 9.3, "vector": "AV:NETWORK/AC:MEDIUM/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "nessus": [{"lastseen": "2021-01-01T05:43:30", "description": "The remote Windows host is running a version of Microsoft Word or\nWord Viewer that is affected by several vulnerabilities. If an\nattacker can trick a user on the affected host into opening a\nspecially crafted Word file, he could leverage this issue to execute\narbitrary code subject to the user's privileges.", "edition": 28, "published": "2010-08-11T00:00:00", "title": "MS10-056: Vulnerability in Microsoft Office Word Could Allow Remote Code Execution (2269638)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2010-1901", "CVE-2010-1903", "CVE-2010-1902", "CVE-2010-1900"], "modified": "2021-01-02T00:00:00", "cpe": ["cpe:/a:microsoft:word", "cpe:/a:microsoft:works", "cpe:/a:microsoft:word_viewer", "cpe:/a:microsoft:office", "cpe:/a:microsoft:office_compatibility_pack"], "id": "SMB_NT_MS10-056.NASL", "href": "https://www.tenable.com/plugins/nessus/48293", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(48293);\n script_version(\"1.30\");\n script_cvs_date(\"Date: 2018/11/15 20:50:30\");\n\n script_cve_id(\n \"CVE-2010-1900\",\n \"CVE-2010-1901\",\n \"CVE-2010-1902\",\n \"CVE-2010-1903\"\n );\n script_bugtraq_id(\n 42130,\n 42132,\n 42133,\n 42136\n );\n script_xref(name:\"MSFT\", value:\"MS10-056\");\n script_xref(name:\"MSKB\", value:\"2251389\");\n script_xref(name:\"MSKB\", value:\"2251399\");\n script_xref(name:\"MSKB\", value:\"2251419\");\n script_xref(name:\"MSKB\", value:\"2251437\");\n script_xref(name:\"MSKB\", value:\"2277947\");\n\n script_name(english:\"MS10-056: Vulnerability in Microsoft Office Word Could Allow Remote Code Execution (2269638)\");\n script_summary(english:\"Checks version of Word\");\n\n script_set_attribute(\n attribute:\"synopsis\",\n value:\n\"Arbitrary code can be executed on the remote host through Microsoft\nWord.\"\n );\n script_set_attribute(\n attribute:\"description\",\n value:\n\"The remote Windows host is running a version of Microsoft Word or\nWord Viewer that is affected by several vulnerabilities. If an\nattacker can trick a user on the affected host into opening a\nspecially crafted Word file, he could leverage this issue to execute\narbitrary code subject to the user's privileges.\"\n );\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2010/ms10-056\");\n script_set_attribute(\n attribute:\"solution\",\n value:\n\"Microsoft has released a set of patches for Office XP, Word 2003, and\nWord Viewer.\"\n );\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\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2010/08/10\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2010/08/10\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2010/08/11\");\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 script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_copyright(english:\"This script is Copyright (C) 2010-2018 Tenable Network Security, Inc.\");\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\n\ninclude(\"smb_func.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"misc_func.inc\");\ninclude(\"audit.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS10-056';\nkbs = make_list(\"2251389\", \"2251399\", \"2251419\", \"2251437\", \"2277947\");\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\ninfo = \"\";\n\nvuln = 0;\nkb = \"\";\n# Word.\ninstalls = get_kb_list(\"SMB/Office/Word/*/ProductPath\");\nif (!isnull(installs))\n{\n foreach install (keys(installs))\n {\n version = install - 'SMB/Office/Word/' - '/ProductPath';\n path = installs[install];\n if (isnull(path)) path = 'n/a';\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 # Word 2007.\n office_sp = get_kb_item(\"SMB/Office/2007/SP\");\n if (\n (!isnull(office_sp) && office_sp == 2) &&\n (\n ver[0] == 12 && ver[1] == 0 &&\n (\n ver[2] < 6541 ||\n (ver[2] == 6541 && ver[3] < 5000)\n )\n )\n )\n {\n vuln++;\n info =\n '\\n Product : Word 2007' +\n '\\n File : ' + path +\n '\\n Installed version : ' + version +\n '\\n Fixed version : 12.0.6541.5000' + '\\n';\n kb = '2251419';\n hotfix_add_report(info, bulletin:bulletin, kb:kb);\n }\n\n # Word 2003.\n office_sp = get_kb_item(\"SMB/Office/2003/SP\");\n if (\n (!isnull(office_sp) && office_sp == 3) &&\n (ver[0] == 11 && ver[1] == 0 && ver[2] < 8326)\n )\n {\n vuln++;\n info =\n '\\n Product : Word 2003' +\n '\\n File : ' + path +\n '\\n Installed version : ' + version +\n '\\n Fixed version : 11.0.8326.0' + '\\n';\n kb = '2251399';\n hotfix_add_report(info, bulletin:bulletin, kb:kb);\n }\n\n # Word 2002.\n office_sp = get_kb_item(\"SMB/Office/XP/SP\");\n if (\n (!isnull(office_sp) && office_sp == 3) &&\n (ver[0] == 10 && ver[1] == 0 && ver[2] < 6864)\n )\n {\n vuln++;\n info =\n '\\n Product : Word 2002' +\n '\\n File : ' + path +\n '\\n Installed version : ' + version +\n '\\n Fixed version : 10.0.6864.0' + '\\n';\n kb = '2251389';\n hotfix_add_report(info, bulletin:bulletin, kb:kb);\n }\n }\n}\n\n\n# Word Viewer.\ninstalls = get_kb_list(\"SMB/Office/WordViewer/*/ProductPath\");\nif (!isnull(installs))\n{\n foreach install (keys(installs))\n {\n version = isntall - 'SMB/Office/WordViewer/' - '/ProductPath';\n path = installs[install];\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 # Word Viewer 2003.\n if (ver[0] == 11 && ver[1] == 0 && ver[2] < 8326)\n {\n vuln++;\n info =\n '\\n Product : Word Viewer 2003' +\n '\\n File : ' + path +\n '\\n Installed version : ' + version +\n '\\n Fixed version : 11.0.8326.0' + '\\n';\n kb = '2251437';\n hotfix_add_report(info, bulletin:bulletin, kb:kb);\n }\n }\n}\n\n# 2007 Microsoft Office system and the Microsoft Office Compatibility Pack.\nshare = '';\nlastshare = '';\naccessibleshare = FALSE;\ninstalls = get_kb_list(\"SMB/Ofice/WordCnv/*/ProductPath\");\nif (!isnull(installs))\n{\n foreach install (keys(installs))\n {\n version = install - 'SMB/Office/WordCnv/' - '/ProductPath';\n path = installs[install];\n share = hotfix_path2share(path:path);\n if (share != lastshare || !accessibleshare)\n {\n lastshare = share;\n if (!is_accessible_share(share:share)) accessibleshare = FALSE;\n else accessibleshare = TRUE;\n }\n if (accessibleshare)\n {\n path = path - 'Wordconv.exe';\n\n if (hotfix_check_fversion(path:path, file:\"wordcnv.dll\", version:\"12.0.6539.5000\", bulletin:bulletin, kb:'2277947') == HCF_OLDER)\n {\n vuln++;\n }\n }\n }\n hotfix_check_fversion_end();\n}\n\nif (vuln)\n{\n set_kb_item(name:'SMB/Missing/MS10-056', value:TRUE);\n hotfix_security_hole();\n exit(0);\n}\nelse audit(AUDIT_HOST_NOT, 'affected');\n", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}}]}