MS05-013: Vulnerability in the DHTML Editing Component may allow code execution (891781)
2005-02-08T00:00:00
ID SMB_NT_MS05-013.NASL Type nessus Reporter This script is Copyright (C) 2005-2018 Tenable Network Security, Inc. Modified 2021-01-02T00:00:00
Description
The remote host is running a version of Windows which contains a flaw
in the DHTML Editing Component ActiveX Control.
An attacker could exploit this flaw to execute arbitrary code on the
remote host.
To exploit this flaw, an attacker would need to construct a malicious
web page and lure a victim into visiting it.
#
# (C) Tenable Network Security, Inc.
#
include("compat.inc");
if (description)
{
script_id(16329);
script_version("1.37");
script_cvs_date("Date: 2018/11/15 20:50:29");
script_cve_id("CVE-2004-1319");
script_bugtraq_id(11950);
script_xref(name:"MSFT", value:"MS05-013");
script_xref(name:"CERT", value:"356600");
script_xref(name:"MSKB", value:"891781");
script_name(english:"MS05-013: Vulnerability in the DHTML Editing Component may allow code execution (891781)");
script_summary(english:"Checks for KB 891781 via the registry");
script_set_attribute(attribute:"synopsis", value:
"Arbitrary code can be executed on the remote host through the web
client.");
script_set_attribute(attribute:"description", value:
"The remote host is running a version of Windows which contains a flaw
in the DHTML Editing Component ActiveX Control.
An attacker could exploit this flaw to execute arbitrary code on the
remote host.
To exploit this flaw, an attacker would need to construct a malicious
web page and lure a victim into visiting it.");
script_set_attribute(attribute:"see_also", value:"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2005/ms05-013");
script_set_attribute(attribute:"solution", value:
"Microsoft has released a set of patches for Windows 2000, XP and
2003.");
script_set_cvss_base_vector("CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C");
script_set_cvss_temporal_vector("CVSS2#E:H/RL:OF/RC:C");
script_set_attribute(attribute:"exploitability_ease", value:"Exploits are available");
script_set_attribute(attribute:"exploit_available", value:"true");
script_set_attribute(attribute:"exploited_by_malware", value:"true");
script_set_attribute(attribute:"vuln_publication_date", value:"2004/12/15");
script_set_attribute(attribute:"patch_publication_date", value:"2005/02/08");
script_set_attribute(attribute:"plugin_publication_date", value:"2005/02/08");
script_set_attribute(attribute:"plugin_type", value:"local");
script_set_attribute(attribute:"cpe", value:"cpe:/o:microsoft:windows");
script_end_attributes();
script_category(ACT_GATHER_INFO);
script_copyright(english:"This script is Copyright (C) 2005-2018 Tenable Network Security, Inc.");
script_family(english:"Windows : Microsoft Bulletins");
script_dependencies("smb_hotfixes.nasl" , "ms_bulletin_checks_possible.nasl");
script_require_keys("SMB/MS_Bulletin_Checks/Possible");
script_require_ports(139, 445, 'Host/patch_management_checks');
exit(0);
}
include("audit.inc");
include("smb_hotfixes_fcheck.inc");
include("smb_hotfixes.inc");
include("smb_func.inc");
include("misc_func.inc");
get_kb_item_or_exit("SMB/MS_Bulletin_Checks/Possible");
bulletin = 'MS05-013';
kb = '891781';
kbs = make_list(kb);
if (get_kb_item("Host/patch_management_checks")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);
get_kb_item_or_exit("SMB/Registry/Enumerated");
get_kb_item_or_exit("SMB/WindowsVersion", exit_code:1);
if (hotfix_check_sp_range(win2k:'3,4', xp:'1,2', win2003:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);
path = hotfix_get_commonfilesdir();
if (!path) exit(1, "Failed to get the Common Files directory.");
share = hotfix_path2share(path:path);
if (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);
if (
hotfix_is_vulnerable(os:"5.2", sp:0, file:"Dhtmled.ocx", version:"6.1.0.9231", path:path, dir:"\Microsoft Shared\Triedit", bulletin:bulletin, kb:kb) ||
hotfix_is_vulnerable(os:"5.1", file:"Dhtmled.ocx", version:"6.1.0.9232", path:path, dir:"\Microsoft Shared\Triedit", bulletin:bulletin, kb:kb) ||
hotfix_is_vulnerable(os:"5.0", file:"Dhtmled.ocx", version:"6.1.0.9232", path:path, dir:"\Microsoft Shared\Triedit", bulletin:bulletin, kb:kb)
)
{
set_kb_item(name:"SMB/Missing/"+bulletin, value:TRUE);
hotfix_security_hole();
hotfix_check_fversion_end();
exit(0);
}
else
{
hotfix_check_fversion_end();
audit(AUDIT_HOST_NOT, 'affected');
}
{"id": "SMB_NT_MS05-013.NASL", "bulletinFamily": "scanner", "title": "MS05-013: Vulnerability in the DHTML Editing Component may allow code execution (891781)", "description": "The remote host is running a version of Windows which contains a flaw\nin the DHTML Editing Component ActiveX Control.\n\nAn attacker could exploit this flaw to execute arbitrary code on the\nremote host.\n\nTo exploit this flaw, an attacker would need to construct a malicious\nweb page and lure a victim into visiting it.", "published": "2005-02-08T00:00:00", "modified": "2021-01-02T00:00:00", "cvss": {"score": 9.3, "vector": "AV:N/AC:M/Au:N/C:C/I:C/A:C"}, "href": "https://www.tenable.com/plugins/nessus/16329", "reporter": "This script is Copyright (C) 2005-2018 Tenable Network Security, Inc.", "references": ["https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2005/ms05-013"], "cvelist": ["CVE-2004-1319"], "type": "nessus", "lastseen": "2021-01-01T05:43:22", "edition": 27, "viewCount": 18, "enchantments": {"dependencies": {"references": [{"type": "cve", "idList": ["CVE-2004-1319"]}, {"type": "osvdb", "idList": ["OSVDB:12424"]}, {"type": "cert", "idList": ["VU:356600"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:7763"]}], "modified": "2021-01-01T05:43:22", "rev": 2}, "score": {"value": 6.4, "vector": "NONE", "modified": "2021-01-01T05:43:22", "rev": 2}, "vulnersScore": 6.4}, "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(16329);\n script_version(\"1.37\");\n script_cvs_date(\"Date: 2018/11/15 20:50:29\");\n\n script_cve_id(\"CVE-2004-1319\");\n script_bugtraq_id(11950);\n script_xref(name:\"MSFT\", value:\"MS05-013\");\n script_xref(name:\"CERT\", value:\"356600\");\n script_xref(name:\"MSKB\", value:\"891781\");\n\n script_name(english:\"MS05-013: Vulnerability in the DHTML Editing Component may allow code execution (891781)\");\n script_summary(english:\"Checks for KB 891781 via the registry\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"Arbitrary code can be executed on the remote host through the web\nclient.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host is running a version of Windows which contains a flaw\nin the DHTML Editing Component ActiveX Control.\n\nAn attacker could exploit this flaw to execute arbitrary code on the\nremote host.\n\nTo exploit this flaw, an attacker would need to construct a malicious\nweb page and lure a victim into visiting it.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2005/ms05-013\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP and\n2003.\");\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:\"2004/12/15\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2005/02/08\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2005/02/08\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n\n script_copyright(english:\"This script is Copyright (C) 2005-2018 Tenable Network Security, Inc.\");\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_dependencies(\"smb_hotfixes.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 exit(0);\n}\n\ninclude(\"audit.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_func.inc\");\ninclude(\"misc_func.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS05-013';\nkb = '891781';\n\nkbs = make_list(kb);\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit(\"SMB/Registry/Enumerated\");\nget_kb_item_or_exit(\"SMB/WindowsVersion\", exit_code:1);\n\nif (hotfix_check_sp_range(win2k:'3,4', xp:'1,2', win2003:'0') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\npath = hotfix_get_commonfilesdir();\nif (!path) exit(1, \"Failed to get the Common Files directory.\");\n\nshare = hotfix_path2share(path:path);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"Dhtmled.ocx\", version:\"6.1.0.9231\", path:path, dir:\"\\Microsoft Shared\\Triedit\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", file:\"Dhtmled.ocx\", version:\"6.1.0.9232\", path:path, dir:\"\\Microsoft Shared\\Triedit\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.0\", file:\"Dhtmled.ocx\", version:\"6.1.0.9232\", path:path, dir:\"\\Microsoft Shared\\Triedit\", bulletin:bulletin, kb:kb)\n)\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, 'affected');\n}\n", "naslFamily": "Windows : Microsoft Bulletins", "pluginID": "16329", "cpe": ["cpe:/o:microsoft:windows"], "scheme": null}
{"cve": [{"lastseen": "2020-10-03T11:33:40", "description": "The DHTML Edit Control (dhtmled.ocx) allows remote attackers to inject arbitrary web script into other domains by setting a name for a window, opening a child page whose target is the window with the given name, then injecting the script from the parent into the child using execScript, as demonstrated by \"AbusiveParent\" in Internet Explorer 6.0.2900.2180.", "edition": 3, "cvss3": {}, "published": "2004-12-15T05:00:00", "title": "CVE-2004-1319", "type": "cve", "cwe": ["NVD-CWE-Other"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 10.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "NONE", "availabilityImpact": "NONE", "integrityImpact": "PARTIAL", "baseScore": 5.0, "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 2.9, "obtainUserPrivilege": false}, "cvelist": ["CVE-2004-1319"], "modified": "2019-04-30T14:27:00", "cpe": ["cpe:/o:microsoft:windows_me:*", "cpe:/o:microsoft:windows_2003_server:enterprise", "cpe:/a:nortel:ip_softphone_2050:*", "cpe:/o:microsoft:windows_2003_server:standard", "cpe:/o:microsoft:windows_2003_server:web", "cpe:/o:microsoft:windows_98se:*", "cpe:/o:microsoft:windows_98:*", "cpe:/o:microsoft:windows_2000:*", "cpe:/o:microsoft:windows_2003_server:r2", "cpe:/a:nortel:mobile_voice_client_2050:*", "cpe:/o:microsoft:windows_xp:*", "cpe:/o:microsoft:windows_2003_server:enterprise_64-bit", "cpe:/a:nortel:optivity_telephony_manager:*"], "id": "CVE-2004-1319", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2004-1319", "cvss": {"score": 5.0, "vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N"}, "cpe23": ["cpe:2.3:o:microsoft:windows_2003_server:r2:*:64-bit:*:*:*:*:*", "cpe:2.3:a:nortel:mobile_voice_client_2050:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:standard:*:64-bit:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp2:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:enterprise_64-bit:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:64-bit:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:r2:*:datacenter_64-bit:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:enterprise:*:64-bit:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp3:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:web:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_98:*:gold:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp1:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp4:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:gold:professional:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:tablet_pc:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:home:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:home:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_me:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:media_center:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_98se:*:*:*:*:*:*:*:*", "cpe:2.3:a:nortel:ip_softphone_2050:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:64-bit:*:*:*:*:*", "cpe:2.3:a:nortel:optivity_telephony_manager:*:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:home:*:*:*:*:*"]}], "cert": [{"lastseen": "2020-09-18T20:43:40", "bulletinFamily": "info", "cvelist": ["CVE-2004-1319"], "description": "### Overview \n\nA cross-domain vulnerability exists in the DHTML Editing ActiveX control. An attacker may be able to execute arbitrary script in the Local Machine Zone or read or modify data in other domains. For example, the attacker could execute arbitrary commands with parameters, download and execute arbitrary code, read cookies, spoof content, or modify form behavior. \n\n### Description \n\n**The Cross-Domain Security Model ** \n\n\nIE uses a cross-domain security model to maintain separation between browser frames from different sources. This model is designed to prevent code in one domain from accessing data in a different domain. The [Internet Security Manager Object](<http://msdn.microsoft.com/workshop/security/szone/reference/objects/internetsecuritymanager.asp>) determines which zone or domain a URL exists in and what actions can be performed. From Microsoft Security Bulletin [MS03-048](<http://www.microsoft.com/technet/security/bulletin/MS03-048.asp>): \n \n_One of the principal security functions of a browser is to ensure that browser windows that are under the control of different Web sites cannot interfere with each other or access each other's data, while allowing windows from the same site to interact with each other. To differentiate between cooperative and uncooperative browser windows, the concept of a \"domain\" has been created. A domain is a security boundary - any open windows within the same domain can interact with each other, but windows from different domains cannot. The cross-domain security model is the part of the security architecture that keeps windows from different domains from interfering with each other._ \n**The DHTML Editing Control** \n \nThe [DHTML Editing Control](<http://activex.microsoft.com/activex/controls/dhtmled/dhtmled.asp>) is a wrapper for the [MSHTML editor](<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmshtml/html/mshtmleditplatf.asp>). It is an ActiveX control that provides the ability to perform text and HTML editing functions. The control is marked \"safe for scripting,\" which means that the DHTML Editing Control could be called from Internet Explorer. The `LoadURL` method, which is traditionally used to open web page content in the DHTML Editing Control, will only open documents in the same domain as the host page. When used with a certain combination of script commands, the DHTML Editing Control can open the content of an arbitrary web page in any domain, regardless of the domain of the host page. \n \n**The Problem** \n \nThe DHTML Editing Control is vulnerable to a cross-domain violation. When the DHTML Editing Control opens the content from a website, it appears to operate within the security context of that website. While the DHTML Editing Control has the security context of the opened site, the DHTML Editing Control is under full control of the page that hosts it. Working indirectly through the DHTML Editing Control, a website in one domain has the ability to access information in another domain or zone. \n \n--- \n \n### Impact \n\nBy convincing a user to view a specially crafted HTML document (e.g., a web page or an HTML email message), an attacker may be able to execute script in the Local Machine Zone. Script that executes in the Local Machine Zone can be used to download and execute arbitrary code. An attacker may obtain full access to web content in another domain, which may reside in a different security zone. The impact is similar to that of a cross-site scripting vulnerability. This includes the ability to spoof or modify web content, access website information such as cookies, or retrieve data from an encrypted HTTPS connection. For a more detailed description of the impact of cross-site scripting vulnerabilities, please see CERT Advisory [CA-2000-02](<http://www.cert.org/advisories/CA-2000-02.html#impact>). \n \n--- \n \n### Solution \n\n**Install an update** \nInstall the update referenced in [MS05-013](<http://www.microsoft.com/technet/security/bulletin/ms05-013.mspx>). With this update, the cross-domain security model is enforced with the DHTML Editing Control. \n \n--- \n \n \n**Disable the DHTML Editing Control** \n \nDisable the DHTML Editing Control by setting the kill bit as described in [Microsoft Knowledge Base article 240797](<http://support.microsoft.com/kb/240797>). The CLSID for the DHTML Editing Control is: \n \n`{2D360201-FFF5-11d1-8D03-00A0C959B``C0A}` \nNote that disabling the DHTML Editing Control may prevent Outlook Web Access (OWA) from functioning properly[](<http://support.microsoft.com/?kbid=298110>). \n[](<http://support.microsoft.com/?kbid=298110>) \n**Disable Active scripting and ActiveX** \n \nDisabling Active scripting and ActiveX controls in the Internet Zone (or any zone used by an attacker) appears to prevent exploitation of this vulnerability. With ActiveX controls disabled, the DHTML Editing Control will not be instantiated. Instructions for disabling Active scripting in the Internet Zone can be found in the [Malicious Web Scripts FAQ](<http://www.cert.org/tech_tips/malicious_code_FAQ.html#ie56>). See Microsoft Knowledge Base Article [833633](<http://support.microsoft.com/default.aspx?scid=833633>) for information about securing the Local Machine Zone, and [315933](<http://support.microsoft.com/?kbid=315933>) for information about displaying the Local Machine Zone (My Computer security zone) on the Security tab in the Internet Options dialog box. \n \nNote that disabling Active scripting and ActiveX controls in the Internet Zone will reduce the functionality of some web sites. Disabling these features in the Local Machine Zone will reduce the functionality of some programs, including the Help and Support Center in Windows XP. \n \n**Install Windows XP Service Pack 2 (SP2)** \n \nMicrosoft [Windows XP SP2](<http://www.microsoft.com/technet/prodtechnol/winxppro/sp2preview.mspx>) includes a feature called [Local Machine Zone Lockdown](<http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2brows.mspx#EHAA>), as well as other improvements. The Local Machine Zone Lockdown prevents Internet Explorer and several other programs from evaluating script in the Local Machine Zone. While this does not remove the vulnerability, it does help prevent an attacker from executing script in the Local Machine Zone. \n \n**Apply the Outlook Email Security Update** \n \nAnother way to effectively disable Active scripting in Outlook is to install the Outlook Email Security Update. The update configures Outlook to open email messages in the Restricted Sites Zone, where Active scripting is disabled by default. In addition, the update provides further protection against malicious code that attempts to propagate via Outlook. The Outlook Email Security Update is available for [Outlook 98](<http://office.microsoft.com/downloads/9798/Out98sec.aspx>) and [Outlook 2000](<http://office.microsoft.com/downloads/2000/Out2ksec.aspx>). The functionality of the Outlook Email Security Update is included in Outlook 2002 and Outlook Express 6. Outlook 2003 includes these and other security enhancements. \n \n**Read and send email in plain text format** \n \nOutlook 2003, Outlook 2002 SP1, and Outlook 6 SP1 can be configured to view email messages in text format. Consider the security of fellow Internet users and send email in plain text format when possible. Note that reading and sending email in plain text will not necessarily prevent exploitation of this vulnerability. \n \n**Do not follow unsolicited links** \n \nIn order to convince users to visit their sites, attackers often use URL encoding, IP address variations, long URLs, intentional misspellings, and other techniques to create misleading links. Do not click on unsolicited links received in email, instant messages, web forums, or internet relay chat (IRC) channels. Type URLs directly into the browser to avoid these misleading links. While these are generally good security practices, following these behaviors will not prevent exploitation of this vulnerability in all cases, particularly if a trusted site has been compromised or allows cross-site scripting. \n \n**Use a different web browser**\n\nThere are a number of significant vulnerabilities in technologies relating to the IE domain/zone security model, local file system (Local Machine Zone) trust, the Dynamic HTML (DHTML) document object model (in particular, proprietary DHTML features), the HTML Help system, MIME type determination, the graphical user interface (GUI), and ActiveX. These technologies are implemented in operating system libraries that are used by IE and many other programs to provide web browser functionality. IE is integrated into Windows to such an extent that vulnerabilities in IE frequently provide an attacker significant access to the operating system. \n \nIt is possible to reduce exposure to these vulnerabilities by using a different web browser, especially when viewing untrusted HTML documents (e.g., web sites, HTML email messages). Such a decision may, however, reduce the functionality of sites that require IE-specific features such as proprietary DHTML, VBScript, and ActiveX. Note that using a different web browser will not remove IE from a Windows system, and other programs may invoke IE, the WebBrowser ActiveX control (WebOC), or the HTML rendering engine (MSHTML). \n \n--- \n \n### Vendor Information\n\n356600\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Additional information available\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n**Javascript is disabled. Click here to view vendors.**\n\n### Avaya __ Affected\n\nUpdated: February 17, 2005 \n\n### Status\n\nAffected\n\n### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Vendor Information \n\nThe vendor has not provided us with any further information regarding this vulnerability.\n\n### Addendum\n\nPlease see the [Avaya Security Advisory](<http://support.avaya.com/elmodocs2/security/ASA-2005-037_MS05-004-MS05-015.pdf>).\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23356600 Feedback>).\n\n### Microsoft Corporation __ Affected\n\nNotified: January 05, 2005 Updated: January 05, 2005 \n\n### Status\n\nAffected\n\n### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Vendor Information \n\nThe vendor has not provided us with any further information regarding this vulnerability.\n\n### Addendum\n\nUS-CERT has no additional comments at this time.\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23356600 Feedback>).\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | | \nTemporal | | \nEnvironmental | | \n \n \n\n\n### References \n\n * <http://secunia.com/advisories/13482/>\n * <http://www.securityfocus.com/bid/11950>\n * <http://www.securitytracker.com/alerts/2004/Dec/1012584.html>\n * <http://xforce.iss.net/xforce/xfdb/18504>\n * <http://freehost07.websamba.com/greyhats/abusiveparent-discussion.htm>\n * <http://activex.microsoft.com/activex/controls/dhtmled/dhtmled.asp>\n * <http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaredcom/html/cncpt.asp>\n * <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmshtml/html/mshtmleditplatf.asp>\n * <http://www.cert.org/advisories/CA-2000-02.html#impact>\n * <http://www.cert.org/tech_tips/malicious_code_FAQ.html#ie56>\n * <http://support.microsoft.com/?kbid=833633>\n * <http://support.microsoft.com/?kbid=315933>\n * <http://support.microsoft.com/?kbid=240797>\n * <http://support.microsoft.com/?kbid=298110>\n * <http://www.antiphishing.org/consumer_recs.html>\n\n### Acknowledgements\n\nThis vulnerability was publicly reported by Paul.\n\nThis document was written by Will Dormann.\n\n### Other Information\n\n**CVE IDs:** | [CVE-2004-1319](<http://web.nvd.nist.gov/vuln/detail/CVE-2004-1319>) \n---|--- \n**Severity Metric:** | 35.10 \n**Date Public:** | 2004-12-15 \n**Date First Published:** | 2005-01-05 \n**Date Last Updated: ** | 2005-02-17 16:36 UTC \n**Document Revision: ** | 29 \n", "modified": "2005-02-17T16:36:00", "published": "2005-01-05T00:00:00", "id": "VU:356600", "href": "https://www.kb.cert.org/vuls/id/356600", "type": "cert", "title": "Microsoft Internet Explorer DHTML Editing ActiveX control contains a cross-domain vulnerability", "cvss": {"score": 5.0, "vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:11", "bulletinFamily": "software", "cvelist": ["CVE-2004-1319"], "description": "Microsoft Security Bulletin MS05-013\r\nVulnerability in the DHTML Editing Component ActiveX Control Could Allow Remote Code Execution (891781)\r\n\r\nIssued: February 8, 2005\r\nVersion: 1.0\r\n\r\nSummary\r\nWho should read this document: Customers who use Microsoft Windows\r\n\r\nImpact of Vulnerability: Remote Code Execution\r\n\r\nMaximum Severity Rating: Critical\r\n\r\nRecommendation: Customers should apply the update immediately.\r\n\r\nSecurity Update Replacement: None\r\n\r\nCaveats: Microsoft Knowledge Base Article 891781 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 891781.\r\n\r\nTested Software and Security Update Download Locations:\r\n\r\nAffected Software: \r\n\r\n\u2022 Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows Server 2003 \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows Server 2003 for Itanium-based Systems \u2013 Download the update\r\n \r\n\u2022 Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) \u2013 Review the FAQ section of this bulletin for details about these operating systems.\r\n \r\n\r\nThe software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nTop of section\r\nGeneral Information\r\n Executive Summary \r\n\r\nExecutive Summary:\r\n\r\nThis update resolves a newly-discovered, public vulnerability. A vulnerability exists in the DHTML Editing Component ActiveX Control. This vulnerability could allow information disclosure or remote code execution on an affected system. The vulnerability is documented in the \u201cVulnerability Details\u201d section of this bulletin.\r\n\r\nIf a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.\r\n\r\nWe recommend that customers apply the update immediately.\r\n\r\nSeverity Ratings and Vulnerability Identifiers:\r\n\r\nVulnerability Identifiers Impact of Vulnerability Windows 98, 98 SE, ME Windows 2000 Windows XP Windows XP Service Pack 2 Windows Server 2003 \r\nDHTML Editing Component ActiveX Control Cross Domain Vulnerability - CAN-2004-1319\r\n Remote Code Execution\r\n Critical\r\n Critical\r\n Critical\r\n Important\r\n Moderate\r\n \r\n\r\nThis assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.\r\n\r\nTop of section\r\n Frequently asked questions (FAQ) related to this security update \r\n\r\nHow does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?\r\nMicrosoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.\r\n\r\nFor more information about severity ratings, visit the following Web site.\r\n\r\nAre Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?\r\nYes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. A Critical security update for these platforms is available, is provided as part of this security bulletin, and can be downloaded only from the Windows Update Web site. For more information about severity ratings, visit the following Web site.\r\n\r\nNote Updates for localized versions of Microsoft Windows 98, Microsoft Windows 98 Second Edition, and Windows Millennium Edition that are not supported by Windows Update. Updates for these versions are available for download at the following download locations:\r\n\r\n\u2022 Slovenian \u2013 Download the update\r\n \r\n\u2022 Slovakian \u2013 Download the update\r\n \r\n\r\nI am still using Windows XP, but extended security update support ended on September 30th, 2004. What should I do?\r\n\r\nThe original version of Windows XP, generally known as Windows XP Gold or Windows XP Release to Manufacturing (RTM) version, reached the end of its extended security update support life cycle on September 30, 2004.\r\n\r\nIt should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Service Pack Product Lifecycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Lifecycle, visit the Microsoft Support Lifecycle Web site.\r\n\r\nFor more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nI am still using Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?\r\n\r\nWindows 2000 Service Pack 2 reached the end of its extended support life cycle as previously documented. It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the Microsoft Support Lifecycle Web site. For more information about the extended security update support period for this operating system version, visit the Microsoft Product Support Services Web site.\r\n\r\nFor more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nExtended security update support for Microsoft Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT 4.0 Server Service Pack 6a ended on December 31, 2004. I\u2019m still using one of these operating systems, what should I do?\r\n\r\nWindows NT 4.0 Workstation Service Pack 6a, Windows NT 4.0 Server Service Pack 6a, and Windows 2000 Service Pack 2 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.\r\n\r\nCustomers who require additional support for Windows NT 4.0 SP6a must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.\r\n\r\nFor more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nI am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability?\r\nYes. By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Internet Explorer Enhanced Security Configuration. This mode mitigates this issue.\r\n\r\nWhat is Internet Explorer Enhanced Security Configuration?\r\nInternet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:\r\n\r\n\u2022 Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.\r\n \r\n\u2022 Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.\r\n \r\n\u2022 Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.\r\n \r\n\u2022 Multimedia content is disabled. This setting prevents music, animations, and video clips from running.\r\n \r\n\r\nI am running Internet Explorer on Windows XP Service Pack 2. Does this mitigate this vulnerability?\r\nYes. Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown that mitigates this vulnerability.\r\n\r\nWhat is the Local Machine zone lockdown?\r\nIn Windows XP Service Pack 2, all local files and content that are processed by Internet Explorer has additional security applied to it in the Local Machine zone. This feature restricts HTML in the Local Machine zone. This feature also restricts HTML that is hosted in Internet Explorer. These restrictions help mitigate attacks where the Local Machine zone is used as an attack vector to load malicious HTML code.\r\n\r\nBecause of this change, ActiveX script in local HTML pages that are viewed inside Internet Explorer will not run. Also, script in local HTML pages that are viewed inside Internet Explorer prompts the user for permission to run.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?\r\nYes. MBSA will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.\r\n\r\nNote After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date by using MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2.1 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2.1 Q&A Web site.\r\n\r\nCan I use Systems Management Server (SMS) to determine whether this update is required?\r\nYes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.\r\n\r\nThe Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.\r\n\r\nTop of section\r\n Vulnerability Details \r\n\r\n DHTML Editing Component ActiveX Control Cross Domain Vulnerability - CAN-2004-1319: \r\n\r\nA cross-domain vulnerability exists in the Microsoft Dynamic HTML (DHTML) Editing Component ActiveX control that could allow information disclosure or remote code execution on an affected system. An attacker could exploit the vulnerability by constructing a malicious Web page that could potentially allow remote code execution if a user visited that page. An attacker who successfully exploited this vulnerability could take complete control of an affected system.\r\n\r\n Mitigating Factors for DHTML Editing Component ActiveX Control Cross Domain Vulnerability - CAN-2004-1319: \r\n\r\n\u2022 In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker could also attempt to compromise a Web site to have it display a Web page with malicious content. An attacker would have no way to force users to visit a Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site or to a site that has been compromised by the attacker.\r\n \r\n\u2022 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\n\u2022 By default, Microsoft Outlook Express 6, Outlook 2000, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.\r\n\r\nThe risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:\r\n\r\n\u2022 Install the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.\r\n \r\n\u2022 Use Microsoft Outlook Express 6 or a later version in its default configuration, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default configuration.\r\n \r\n \r\n\u2022 By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability. See the FAQ section for this security update for more information about Internet Explorer Enhanced Security Configuration.\r\n \r\n\u2022 Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown. This security enhancement mitigates this vulnerability. See the FAQ section for this security update for more information about Local Machine zone lockdown.\r\n \r\n\r\nTop of section\r\n Workarounds for DHTML Editing Component ActiveX Control Cross Domain Vulnerability - CAN-2004-1319: \r\n\r\nMicrosoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\r\n\u2022 Set Internet and Local intranet security zone settings to \u201cHigh\u201d to prompt before running ActiveX controls and active scripting in these zones.\r\n\r\nYou can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls and active scripting. You can do this by setting your browser security to High.\r\n\r\nTo raise the browsing security level in Microsoft Internet Explorer, follow these steps:\r\n\r\n1.\r\n On the Internet Explorer Tools menu, click Internet Options.\r\n \r\n2.\r\n In the Internet Options dialog box, click the Security tab, and then click the Internet icon.\r\n \r\n3.\r\n Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.\r\n \r\n\r\nNote If no slider is visible, click Default Level, and then move the slider to High.\r\n\r\nNote Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the high security setting.\r\n\r\nAlternatively, you can change you settings to prompt before running ActiveX controls only. To do this, follow these steps:\r\n\r\n1.\r\n In Internet Explorer, click Internet Options on the Tools menu.\r\n \r\n2.\r\n Click the Security tab.\r\n \r\n3.\r\n Click Internet, and then click Custom Level.\r\n \r\n4.\r\n Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.\r\n \r\n5.\r\n In the Scripting section, under Active Scripting, click Prompt, and then click OK.\r\n \r\n6.\r\n Click Local intranet, and then click Custom Level.\r\n \r\n7.\r\n Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.\r\n \r\n8.\r\n In the Scripting section, under Active Scripting, click Prompt.\r\n \r\n9.\r\n Click OK two times to return to Internet Explorer.\r\n \r\n\r\nImpact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the "Restrict Web sites to only your trusted Web sites" workaround.\r\n \r\n\u2022 Restrict Web sites to only your trusted Web sites.\r\n\r\nAfter you set Internet Explorer to require a prompt before it runs ActiveX controls and active scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to Internet Explorer's Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.\r\n\r\nTo do this, follow these steps:\r\n\r\n1.\r\n In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.\r\n \r\n2.\r\n In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.\r\n \r\n3.\r\n If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.\r\n \r\n4.\r\n In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.\r\n \r\n5.\r\n Repeat these steps for each site that you want to add to the zone.\r\n \r\n6.\r\n Click OK two times to accept the changes and return to Internet Explorer.\r\n \r\n\r\nAdd any sites that you trust not to take malicious action on your computer. One in particular that you may want to add is "*.windowsupdate.microsoft.com" (without the quotation marks). This is the site that will host the update, and it requires an ActiveX control to install the update.\r\n \r\n\u2022 Install the update that is described in Microsoft Security Bulletin MS04-018 if you are using Outlook Express 5.5 SP2.\r\n\r\nOutlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed.\r\n\r\nCustomers running Outlook Express 5.5 Service Pack 2 who have installed Microsoft Security Bulletin MS04-018 could be at a reduced risk from an e-mail-borne attack that tries to exploit this vulnerability unless the user clicks a malicious link in the e-mail message.\r\n \r\n\u2022 Read e-mail messages in plain text format if you are using Outlook 2002 a later version, or Outlook Express 6 SP1 or a later version , to help protect yourself from the HTML e-mail attack vector.\r\n\r\nOutlook 2002 users who have applied Office XP Service Pack 1 or a later version and Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 can enable this setting and view e-mail messages that are not digitally signed, or view 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 enabling 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\r\n\u2022 The changes are applied to the preview pane and to open messages.\r\n \r\n\u2022 Pictures become attachments so that they are not lost.\r\n \r\n\u2022 Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.\r\n \r\n \r\n\u2022 Temporarily disable the DHTML Editing Component ActiveX Control from running in Internet Explorer for Windows XP Service Pack 2.\r\n\r\nYou can help protect against this vulnerability by temporarily disabling the DHTML Editing Component ActiveX Control from running in Internet Explorer. On Windows XP Service Pack 2 use the Internet Explorer Manage Add-ons feature to disable the ActiveX control.\r\n\r\n1.\r\n Start Internet Explorer.\r\n \r\n2.\r\n On the Tools menu, click Manage Add-ons.\r\n \r\n3.\r\n Locate and click on \u201cDHTML Edit Control Safe for Scripting for IE5\u201d.\r\n \r\n4.\r\n To disable the add-on, click Disable, and then click OK.\r\n \r\n\r\nNote If you cannot locate the ActiveX control then use the drop-down box to switch from \u201cAdd-ons currently being used in Internet Explorer\u201d to \u201cAdd-ons that have been used by Internet Explorer\u201d and follow steps 3 and 4. If the ActiveX control is not present in this list either you have not used the ActiveX control before. See the workaround \u201cTemporarily disable the DHTML Editing Component ActiveX Control from running in Internet Explorer\u201d for additional information.\r\n\r\nNote If you use this workaround, you must re-enable this ActiveX control. You should do this after you have applied this security update to regain the functionality that is supplied by the DHTML Editing Component ActiveX Control.\r\n\r\nFor more information on the Internet Explorer Manage Add-ons feature in Windows XP Service Pack 2, see Microsoft Knowledge Base Article 883256.\r\n\r\nImpact of Workaround: Disabling the DHTML Editing Component ActiveX control prevents Internet Explorer from instantiating the control. This configuration causes program compatibility issues. Some examples of such issues include the following:\r\n\r\n\u2022 You cannot compose e-mail messages in Outlook Web Access for Exchange 2000 Server and Exchange Server 2003.\r\n \r\n\u2022 You cannot use Windows SharePoint Services for Windows Server 2003. This product uses the DHTML Editing Component ActiveX control for dynamic Web site HTML editing.\r\n \r\n\u2022 Other Web sites may rely on this ActiveX control for dynamic Web site HTML editing.\r\n \r\n \r\n\u2022 Temporarily disable the DHTML Editing Component ActiveX Control from running in Internet Explorer.\r\n\r\nYou can help protect against this vulnerability by temporarily disabling the DHTML Editing Component ActiveX Control from running in Internet Explorer. To do this, set the kill bit for the control.\r\n\r\nWarning If you use Registry Editor incorrectly, you may cause serious problems that may require that you reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.\r\n\r\nThe class identifier (CLSID) for an ActiveX control is a GUID for that control. You can prevent an ActiveX control from running in Internet Explorer by setting the kill bit so that the control is never called by Internet Explorer. The kill bit is a specific value for the Compatibility Flags DWORD value for the ActiveX control in the registry.\r\n\r\nThe CLSID for the DHTML Editing Component ActiveX Control is {2D360201-FFF5-11D1-8D03-00A0C959BC0A}.\r\n\r\nFor detailed steps that describe how to stop an ActiveX control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow the steps in that article and create a Compatibility Flags DWORD value in the registry to prevent the affected control from being instantiated in Internet Explorer\r\n\r\nNote If you use this workaround, you must reset this registry change by removing the same Compatibility Flags DWORD value from the registry. You should do this after you have applied this security update to regain the functionality that is supplied by the DHTML Editing Component ActiveX Control.\r\n\r\nImpact of Workaround: Disabling the DHTML Editing Component ActiveX control prevents Internet Explorer from instantiating the control. This configuration causes program compatibility issues. Some examples of such issues include the following:\r\n\r\n\u2022 You cannot compose e-mail messages in Outlook Web Access for Exchange 2000 Server and Exchange Server 2003.\r\n \r\n\u2022 You cannot use Windows SharePoint Services for Windows Server 2003. This product uses the DHTML Editing Component ActiveX control for dynamic Web site HTML editing.\r\n \r\n\u2022 Other Web sites may rely on this ActiveX control for dynamic Web site HTML editing.\r\n \r\n \r\n\r\nTop of section\r\n FAQ for DHTML Editing Component ActiveX Control Cross Domain Vulnerability - CAN-2004-1319: \r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a cross-domain vulnerability that could allow information disclosure or remote code execution. If a user is logged on with administrative privileges, 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 privileges. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.\r\n\r\nWhat causes the vulnerability?\r\nThe process by which certain functions that are available through the DHTML Editing Component ActiveX Control are validated by the Internet Explorer cross-domain security model.\r\n\r\nWhat is DHTML Editing Component ActiveX Control?\r\nThe DHTML Editing Component ActiveX control provides an HTML editor that you can use to support dynamic Web site HTML editing in software. For more information about the DHTML Editing Component ActiveX control, see the product documentation.\r\n\r\nWhat are Internet Explorer security zones?\r\nInternet Explorer security zones are part of a system that divides online content into categories or zones based on the trustworthiness of the content. Specific Web domains can be assigned to a zone, depending on how much trust is put in the content of each domain. The zone then restricts the capabilities of the Web content, based on the zone's policy. By default, most Internet domains are treated as part of the Internet zone. By default, the policy of the Internet zone prevents scripts and other active code from accessing resources on the local system.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could run malicious script code in the Local Machine security zone in Internet Explorer. This could allow an attacker to take complete control of the affected system.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nAn attacker could exploit this vulnerability by creating a malicious Web page or an HTML e-mail message and then persuading the user to visit this page or to view the HTML e-mail message. When the user visited the page or viewed the e-mail message, the attacker could access information from other Web sites, local files on the system, or cause script to run in the security context of the Local Machine zone.\r\n\r\nBy default, Microsoft Outlook Express 6, Outlook 2000, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThis vulnerability requires that a user view a Web site or open HTML e-mail messages in a less restrictive Internet Explorer security zone than the Restricted sites zone for malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as users\u2019 workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to visit Web sites, such as most server systems, are at a reduced risk.\r\n\r\nI am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability?\r\nYes. By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Internet Explorer Enhanced Security Configuration. This mode mitigates this vulnerability.\r\n\r\nI am running Internet Explorer on Windows XP Service Pack 2. Does this mitigate this vulnerability?\r\nYes. Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown that mitigates this vulnerability.\r\n\r\nAre Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?\r\nYes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. A Critical security update for these platforms is available, is provided as part of this security bulletin, and can be downloaded only from the Windows Update Web site. For more information about severity ratings, visit the following Web site.\r\n\r\nNote Updates for localized versions of Microsoft Windows 98, Microsoft Windows 98 Second Edition, and Windows Millennium Edition that are not supported by Windows Update. Updates for these versions are available for download at the following download locations:\r\n\r\n\u2022 Slovenian \u2013 Download the update\r\n \r\n\u2022 Slovakian \u2013 Download the update\r\n \r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by validating that the Internet Explorer cross-domain security model is enforced when Internet Explorer uses the DHTML Editing Component ActiveX Control.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nYes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2004-1319.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nYes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.\r\n\r\nTop of section\r\nTop of section\r\nTop of section\r\n Security Update Information \r\n\r\nAffected Software:\r\n\r\nFor information about the specific security update for your affected software, click the appropriate link:\r\n\r\n Windows Server 2003 (all versions) \r\n\r\nPrerequisites\r\nThis security update requires a release version of Windows Server 2003.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in Windows Server 2003 Service Pack 1.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches:\r\n\r\n /help Displays the command-line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\n /uninstall Uninstalls the package\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation has completed\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /l Lists installed Windows hotfixes or update packages\r\n\r\n /o Overwrite OEM files without prompting\r\n\r\n /n Do not backup files needed for uninstall\r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\n /integrate:path Integrates the update into the Windows source files located at the path specified\r\n\r\n /extract Extracts files without starting the Setup program\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb891781-x86-enu /passive /quiet\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb891781-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nRestart Requirement\r\n\r\nThis update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\r\n\r\nRemoval Information\r\n\r\nTo remove this update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB891781$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:\r\n\r\n /help Displays the command line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation is complete\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; and Windows Small Business Server 2003:\r\n\r\nFile Name Version Date Time Size Folder \r\nDhtmled.ocx\r\n 6.1.0.9231\r\n 05-Jan-2005\r\n 00:30\r\n 120,832\r\n RTMGDR\r\n \r\nDhtmled.ocx\r\n 6.1.0.9231\r\n 05-Jan-2005\r\n 00:42\r\n 120,832\r\n RTMQFE\r\n \r\n\r\nWindows Server 2003, Enterprise Edition for Itanium-based Systems and Windows Server 2003, Datacenter Edition for Itanium-based Systems:\r\n\r\nFile Name Version Date Time Size CPU Folder \r\nWdhtmled.ocx\r\n 6.1.0.9231\r\n 12-Jan-2005\r\n 18:41\r\n 120,832\r\n x86\r\n RTMGDR\WOW\r\n \r\nWdhtmled.ocx\r\n 6.1.0.9231\r\n 12-Jan-2005\r\n 18:21\r\n 120,832\r\n x86\r\n RTMQFE\WOW\r\n \r\n\r\nNote When you install this security update on Windows Server 2003, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.\r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nVerifying that the Update Has Been Applied\r\n\r\n\u2022 Microsoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n \r\n\u2022 File Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n Click Start, and then click Search.\r\n \r\n2.\r\n In the Search Results pane, click All files and folders under Search Companion.\r\n \r\n3.\r\n In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n \r\n4.\r\n In the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n \r\n5.\r\n On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n \r\n \r\n\u2022 Registry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB891781\Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 891781 security update into the Windows installation source files.\r\n \r\n\r\nTop of section\r\n Windows XP (all versions) \r\n\r\nPrerequisites\r\nThis security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in a future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches:\r\n\r\n /help Displays the command-line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\n /uninstall Uninstalls the package\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation has completed\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /l Lists installed Windows hotfixes or update packages\r\n\r\n /o Overwrite OEM files without prompting\r\n\r\n /n Do not backup files needed for uninstall\r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\n /integrate:path Integrates the update into the Windows source files located at the path specified\r\n\r\n /extract Extracts files without starting the Setup program\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:\r\n\r\nWindowsxp-kb891781-x86-enu /passive /quiet\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:\r\n\r\nWindowsxp-kb891781-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nRestart Requirement\r\n\r\nIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB891781$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:\r\n\r\n /help Displays the command line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation is complete\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\n\r\nFile Name Version Date Time Size Folder \r\nDhtmled.ocx\r\n 6.1.0.9232\r\n 11-Jan-2005\r\n 01:20\r\n 118,272\r\n SP1QFE\r\n \r\nDhtmled.ocx\r\n 6.1.0.9232\r\n 11-Jan-2005\r\n 01:00\r\n 128,512\r\n SP2GDR\r\n \r\nDhtmled.ocx\r\n 6.1.0.9232\r\n 11-Jan-2005\r\n 01:05\r\n 128,512\r\n SP2QFE\r\n \r\n\r\nWindows XP 64-Bit Edition Service Pack 1 (Itanium):\r\n\r\nFile Name Version Date Time Size CPU \r\nWdhtmled.ocx\r\n 6.1.0.9232\r\n 11-Jan-2005\r\n 01:20\r\n 118,272\r\n x86\r\n \r\n\r\nWindows XP 64-Bit Edition Version 2003 (Itanium):\r\n\r\nFile Name Version Date Time Size CPU Folder \r\nWdhtmled.ocx\r\n 6.1.0.9231\r\n 12-Jan-2005\r\n 18:41\r\n 120,832\r\n x86\r\n RTMGDR\WOW\r\n \r\nWdhtmled.ocx\r\n 6.1.0.9231\r\n 12-Jan-2005\r\n 18:21\r\n 120,832\r\n x86\r\n RTMQFE\WOW\r\n \r\n\r\nNotes The Windows XP and Windows XP 64-Bit Edition Version 2003 (Itanium) versions of this security update are packaged as dual-mode packages. These dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2).\r\n\r\nFor more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.\r\n\r\nWhen you install this security update on Windows XP SP2 or on Windows XP 64-Bit Edition Version 2003 (Itanium), the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:\r\n\r\n\u2022 Windows XP SP2\r\n\r\nThe installer copies the SP2QFE files to your system.\r\n \r\n\u2022 Windows XP 64-Bit Edition Version 2003 (Itanium)\r\n\r\nThe installer copies the RTMQFE files to your system.\r\n \r\n\r\nIf you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:\r\n\r\n\u2022 Windows XP SP2\r\n\r\nThe installer copies the SP2GDR files to your system.\r\n \r\n\u2022 Windows XP 64-Bit Edition Version 2003 (Itanium)\r\n\r\nThe installer copies the RTMGDR files to your system.\r\n \r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nNote For Windows XP 64-Bit Edition Version 2003 (Itanium), this security update is the same as the Windows Server 2003 for Itanium-based Systems security update.\r\n\r\nVerifying that the Update Has Been Applied\r\n\r\n\u2022 Microsoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n \r\n\u2022 File Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n Click Start, and then click Search.\r\n \r\n2.\r\n In the Search Results pane, click All files and folders under Search Companion.\r\n \r\n3.\r\n In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n \r\n4.\r\n In the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n \r\n5.\r\n On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n \r\n \r\n\u2022 Registry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nFor Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB891781\Filelist\r\n\r\nFor Windows XP 64-Bit Edition Version 2003 (Itanium):\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB891781\Filelist\r\n\r\nNote These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 891781 security update into the Windows installation source files.\r\n \r\n\r\nTop of section\r\n Windows 2000 (all versions) \r\n\r\nPrerequisites\r\nFor Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4).\r\n\r\nThe software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nFor more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in a future Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches:\r\n\r\n /help Displays the command-line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\n /uninstall Uninstalls the package\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation has completed\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /l Lists installed Windows hotfixes or update packages\r\n\r\n /o Overwrite OEM files without prompting\r\n\r\n /n Do not backup files needed for uninstall\r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\n /integrate:path Integrates the update into the Windows source files located at the path specified\r\n\r\n /extract Extracts files without starting the Setup program\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:\r\n\r\nWindows2000-kb891781-x86-enu /passive /quiet\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:\r\n\r\nWindows2000-kb891781-x86-enu /norestart\r\n\r\nFor more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.\r\n\r\nRestart Requirement\r\n\r\nThis update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB891781$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:\r\n\r\n /help Displays the command line options\r\n\r\nSetup Modes\r\n\r\n /quiet Quiet mode (no user interaction or display)\r\n\r\n /passive Unattended mode (progress bar only)\r\n\r\nRestart Options \r\n\r\n /norestart Do not restart when installation is complete\r\n\r\n /forcerestart Restart after installation\r\n\r\nSpecial Options \r\n\r\n /f Force other programs to close when the computer shuts down\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows 2000 Service Pack 3 and Windows 2000 Service Pack 4:\r\n\r\nFile Name Version Date Time Size \r\nDhtmled.ocx\r\n 6.1.0.9232\r\n 14-Jan-2005\r\n 01:25\r\n 119,056\r\n \r\n\r\nVerifying that the Update Has Been Applied\r\n\r\n\u2022 Microsoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n \r\n\u2022 File Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n Click Start, and then click Search.\r\n \r\n2.\r\n In the Search Results pane, click All files and folders under Search Companion.\r\n \r\n3.\r\n In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n \r\n4.\r\n In the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n \r\n5.\r\n On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n \r\n \r\n\u2022 Registry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry key:\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB891781\Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 891781 security update into the Windows installation source files.\r\n \r\n\r\nTop of section\r\nTop of section\r\nObtaining Other Security Updates:\r\n\r\nUpdates for other security issues are available at the following locations:\r\n\r\n\u2022 Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."\r\n \r\n\u2022 Updates for consumer platforms are available at the Windows Update Web site.\r\n \r\n\r\nSupport: \r\n\r\n\u2022 Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.\r\n \r\n\u2022 International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.\r\n \r\n\r\nSecurity Resources: \r\n\r\n\u2022 The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.\r\n \r\n\u2022 Microsoft Software Update Services\r\n \r\n\u2022 Microsoft Baseline Security Analyzer (MBSA)\r\n \r\n\u2022 Windows Update \r\n \r\n\u2022 Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.\r\n \r\n\u2022 Office Update \r\n \r\n\r\nSoftware Update Services:\r\n\r\nBy using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.\r\n\r\nFor more information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nSystems Management Server:\r\n\r\nMicrosoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.\r\n\r\nNote SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.\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\n\r\nRevisions: \r\n\r\n\u2022 V1.0 (February 8, 2005): Bulletin published\r\n \r\n", "edition": 1, "modified": "2005-02-08T00:00:00", "published": "2005-02-08T00:00:00", "id": "SECURITYVULNS:DOC:7763", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:7763", "title": "Microsoft Security Bulletin MS05-013 Vulnerability in the DHTML Editing Component ActiveX Control Could Allow Remote Code Execution (891781)", "type": "securityvulns", "cvss": {"score": 5.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}], "osvdb": [{"lastseen": "2017-04-28T13:20:08", "bulletinFamily": "software", "cvelist": ["CVE-2004-1319"], "edition": 1, "description": "## Vulnerability Description\nWindows contains a flaw that allows a remote cross site scripting attack. This flaw exists because dhtmled.ocx does not validate arguments to the execScript() function. This could allow a user to create a specially crafted URL that would execute arbitrary code in a user's browser within the trust relationship between the browser and the server, leading to a loss of integrity.\n## Solution Description\nCurrently, there are no known workarounds or upgrades to correct this issue. However, Microsoft has released a patch to address this vulnerability.\n## Short Description\nWindows contains a flaw that allows a remote cross site scripting attack. This flaw exists because dhtmled.ocx does not validate arguments to the execScript() function. This could allow a user to create a specially crafted URL that would execute arbitrary code in a user's browser within the trust relationship between the browser and the server, leading to a loss of integrity.\n## References:\nSecurity Tracker: 1012584\n[Secunia Advisory ID:13482](https://secuniaresearch.flexerasoftware.com/advisories/13482/)\nOther Advisory URL: http://freehost07.websamba.com/greyhats/abusiveparent.htm\nMicrosoft Security Bulletin: MS05-013\nMail List Post: http://archives.neohapsis.com/archives/bugtraq/2004-12/0167.html\nISS X-Force ID: 18504\n[CVE-2004-1319](https://vulners.com/cve/CVE-2004-1319)\nCERT VU: 356600\nBugtraq ID: 11950\n", "modified": "2004-12-15T06:49:31", "published": "2004-12-15T06:49:31", "href": "https://vulners.com/osvdb/OSVDB:12424", "id": "OSVDB:12424", "type": "osvdb", "title": "Microsoft IE DHTML Edit ActiveX Control execScript() XSS", "cvss": {"score": 5.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:NONE/I:PARTIAL/A:NONE/"}}]}