Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
RE: EEYE: Internet Explorer Object Data Remote Execution Vulnerability
From: Menashe Eliezer (menashefinjan.com)
Date: Fri Aug 22 2003 - 02:24:42 CDT
The ability to launch a local executable file with parameters is very dangerous.
It has been used by MSBlaster/Lovsan worm. (Launching Local tftp.exe)
Finjan Software has modified the basic exploit code that has been published by eEye Digital Security. The following harmless demo creates "YouHaveBeenHacked.vbs" file on "C:\", which shows your login information - User name and domain:
We've decided to limit the distribution of Finjan Software "Auto Disk Format" demo, even though any hacker can create it based on the eEye Digital Security template.
Finjan Software is proactively blocking such demos at both the gateway and desktop levels.
(Including http://www.malware.com/drew.html )
We haven't issued an update for any of our products.
Manager, Malicious Code Research Center
From: Marc Maiffret [mailto:marceeye.com]
Sent: Thursday, August 21, 2003 2:07 AM
Subject: EEYE: Internet Explorer Object Data Remote Execution Vulnerability
Internet Explorer Object Data Remote Execution Vulnerability
August 20, 2003
May 15, 2003
High (Remote Code Execution)
Microsoft Internet Explorer 5.01
Microsoft Internet Explorer 5.5
Microsoft Internet Explorer 6.0
Microsoft Internet Explorer 6.0 for Windows Server 2003
eEye Digital Security has discovered a security vulnerability in Microsoft's
Internet Explorer that would allow executable code to run automatically upon
rendering malicious HTML.
This is a flaw in Microsoft's primary contribution to HTML, the Object tag,
which is used to embed basically all ActiveX into HTML pages. The parameter
that specifies the remote location of data for objects is not checked to
validate the nature of the file being loaded, and therefore trojan
executables may be run from within a webpage as silently and as easily as
Internet Explorer parses image files or any other "safe" HTML content.
This attack may be utilized wherever IE parses HTML, including web sites,
e-mail, newsgroups, and within applications utilizing web-browsing
On Windows 2003 Internet Explorer, this upgrade is noted as being "moderate"
rather than "critical." This is said to be because of Windows 2003's
"Enhanced Security Configuration Mode." In plain English, this just means
that Microsoft checked the "Disable ActiveX" box on Internet Explorer's
Security Properties. Windows 2003 Internet Explorer also disables by default
Due to the popularity and prevalence of ActiveX on the Internet, users
running Windows 2003 "Enhanced Security Configuration" Mode may have chosen
to reactivate the ability to view active content. These users should be
aware that they are at critical risk for this vulnerability and should apply
the necessary patch.
Lastly, Microsoft attributes credit to eEye for this bug, stating it is the
"Object Type" bug. They do this after noting a variant of the "Object Type"
bug was found to be still vulnerable on certain language based systems.
However, the "Object Type" bug was our previous "Object" tag vulnerability.
That issue involved a stack based overflow in the "Type" property. This
current issue involves incorrect handling of the data specified by the
--------------Client HTTP request---------------------------
-------------Server HTTP Response---------------------------
HTTP/1.1 200 OK
Date: Tue, 13 May 2003 18:06:43 GMT
wsh.Run("cmD.exe /k echO so loNg, and ThaNks For all yoUr EmplOyeeS");
This example is in the more traditional vein. In house, we set up a
demonstration system that silently loaded "bo2k" and "subseven" trojans from
within a single webpage.
The above example shows an entirely legitimate session. The only trick to
this is that the "Data" URL must not end in an unsafe extension (e.g.,
".exe", ".bat", etc). The "Content-Type" tag returned by the server is
treated by Internet Explorer as authoritative.
In other words, the client asks for a safe file, the server returns an
unsafe file, and Internet Explorer does not know what hit it.
What Internet Explorer should be doing in this case is not loading the
unsafe document at all, or it should prompt the user with a severe warning
about this file, with the default option being to save the file to disk.
We can generally guess what is going on here. As .hta or "HTML Application"
files are not binary and resemble - mechanically - HTML files, IE's check of
content will be unable to return that this file is anything but safe. The
second check of MIME type will see that we are requesting a safe file
type... and the third check of MIME type will be from the server saying this
is a HTML Application. For whatever reason, IE has ignored the returned MIME
type from a security context, but paid attention to it from an execution
This attack was discovered through manual testing techniques. The hypothesis
was: "Internet Explorer has many avenues where it might be presented with
executable content. One of these avenues must be broken so that executable
content might be automatically run."
Retina Network Security Scanner has been updated to identify this latest
Internet Explorer vulnerability.
Microsoft was notified and has released a patch for this vulnerability. The
patch is available at:
Drew Copley (dcopleyeeye.com), Research Engineer, eEye Digital Security
Greetings: Liu Die Yu, http-equiv, Stone Fisk, Dror Shalev, the Shrug,
Oliver Lavery, Brett Moore, Chung's Donut Shop, Jolly
Copyright (c) 1998-2003 eEye Digital Security
Permission is hereby granted for the redistribution of this alert
electronically. It is not to be edited in any way without express consent of
eEye. If you wish to reprint the whole or any part of this alert in any
other medium excluding electronic medium, please e-mail alerteEye.com for
The information within this paper may change without notice. Use of this
information constitutes acceptance for use in an AS IS condition. There are
NO warranties with regard to this information. In no event shall the author
be liable for any damages whatsoever arising out of or in connection with
the use or spread of this information. Any use of this information is at the
user's own risk.
Please send suggestions, updates, and comments to:
eEye Digital Security