SecurityTracker.com
Keep Track of the Latest Vulnerabilities
with SecurityTracker!
    Home    |    View Topics    |    Search    |    Contact Us    |    Help    |   

SecurityTracker
Archives


Welcome to SecurityTracker!
 
Click to Sign Up
Sign Up
Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Instant Alerts
Buy our Premium Vulnerability Notification Service to receive customized, instant alerts
Affiliates
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Partners
Become a Partner and License Our Database or Notification Service
Report a Bug
Report a vulnerability that you have found to SecurityTracker
bugs
@
securitytracker.com

Sign Up!





Category:  Application (Web Browser)  >  Microsoft Internet Explorer (IE) Vendors:  Microsoft
Microsoft IE dhtmled.ocx Lets Remote Users Execute Cross-Domain Scripting Attacks
SecurityTracker Alert ID:  1012584
SecurityTracker URL:  http://securitytracker.com/id?1012584
CVE Reference:  CAN-2004-1319   (Links to External Site)
Updated:  Feb 8 2005
Original Entry Date:  Dec 16 2004
Impact:  Disclosure of authentication information, Disclosure of user information, Execution of arbitrary code via network, Modification of user information
Exploit Included:  Yes  
Version(s): 6.0
Description:  A vulnerability was reported in Microsoft Internet Explorer (IE) in the DHTML Edit ActiveX control. A remote user can execute scripting code in arbitrary domains.

Paul from GreyHats Security Group reported that a remote user can create HTML that, when loaded by the target user, will invoke the 'dhtmled.ocx' ActiveX control to inject arbitrary scripting code into a different window on the target user's system.

The HTML can open a window and display the page in the control. The parent HTML window can access scripting functions in the new window via the execScript() function.

A demonstration exploit example is available at:

http://freehost07.websamba.com/greyhats/abusiveparent.htm

Impact:  A remote user can execute arbitrary scripting code in an arbitrary domain on the target user's system.
Solution:  No solution was available at the time of this entry.
Vendor URL:  www.microsoft.com/ (Links to External Site)
Cause:  Access control error
Underlying OS:  Windows (Any)
Underlying OS Comments:  Tested only on Windows XP SP2
Reported By:  Paul <paul@greyhats.cjb.net>
Message History:   This archive entry has one or more follow-up message(s) listed below.
Feb 8 2005 (Vendor Issues Fix) Microsoft IE dhtmled.ocx Lets Remote Users Execute Cross-Domain Scripting Attacks
The vendor has issued a fix.



 Source Message Contents

Date:  15 Dec 2004 08:01:33 -0000
From:  Paul <paul@greyhats.cjb.net>
Subject:  MSIE DHTML Edit Control Cross Site Scripting Vulnerability

 



Note: This vulnerability as well as many more can be seen at http://freehost07.websamba.com/greyhats/

MSIE DHTML Edit Control Cross Site Scripting Vulnerability 

[Tested]
IEXPLORE.EXE file version 6.0.2900.2180
MSHTML.DLL file version 6.00.2800.1400
Microsoft Windows XP Home SP2


[Discussion]
I appologize for my previous vulnerability (longnamevuln) which, through default sp2 settings, would 
be quite useless :). However, I'm sure that this will make up for it. While looking at the popup block killer by http-equiv, I became interested in the dhtml edit control.
I had a gut fealing that more could be done than simple popup forcing. So I looked into it and surely enough, I did find something
. For the first time (afaik) since sp1, we can, without user interaction (which I hate btw), inject script into a page that doesn
t belong to us :). While I don't exacly know the specifics of the dhtmled.ocx control, I believe it uses a lot of the sa
me code from old versions of internet explorer. That might explain why it acts so similarly to internet explorer. Through my test
ing, I only found one way to navigate to a page using the dhtml edit control: make it run code to 1) specify its window name, the
n 2) open( ) a page using its new name as the target parameter. This will grab the page and display it in the control. After this,
the control is still accessible by its parent, even Script functions. execScript is what I use to directly inject javascript into th
e control. SP2 puts extremely heavy security on the javascript: and vbscript: protocols, apparently rendering th
em useless for hacking attempts. However, there are still plenty of ways to make a target run script. Hehe this is just like to good
ol' days of sp1 :) The example opens http://google.com in the dhtml edit control and attempts to show the location.href
and document.cookie of the page in a message box. Example at http://freehost07.websamba.com/greyhats/abusiveparent.htm


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us   |    Help

Copyright 2005, SecurityGlobal.net LLC