Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Full-Disclosure] Multiple Backdoors found in eEye Products (IRIS and Secure |
|---|---|
| Date: | Wed, 29 Dec 2004 21:03:02 +0000 |
Hey Dave,
From: Dave Aitel <dave@immunitysec.com>
To: Lance Gusto <thegusto22@hotmail.com>
Subject: Re: [Full-Disclosure] Multiple Backdoors found in eEye Products (IRIS and SecureIIS)
Date: Wed, 29 Dec 2004 11:29:55 -0500
The SecureIIS Backdoor:
The SecureIIS backdoor was alot easier to discover but very well placed. The SecureIIS backdoor is triggered by a specifically crafted HTTP HEAD request. Here is a incomplete layout of how to exploit this:
Which version did you test? I'm not seeing it, or any intermodular calls to CreateProcess in the DLL that it loads up.
-dave
HEAD /<24 byte constant string>/PORT_ADDRESS.ASP HTTP/1.1
PORT - Will be the port to bind a shell. ADDRESS - Address for priority binding (0 - For any).
[snip]
Local Deduction:
There are a two possiblilites here, either eEye's code has been altered by some attacker or this has been sanctioned by the company (or at least the developers were fully aware of this).
Conclusion:
It is very very shameful that a somewhat reputable like eEye is acting in a very childish, unprofessional manner. I figure that is why the code is closed source. There are several active exploits available that I (the author of this advisory) didn't create floating around. The only logical solution will be to not use the mentioned eEye products for the time being or at least downgrade to the non-backdoored versions.
We will be investigation eEye's Blink Product for any clandestine backdoors.
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar ? get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [Full-Disclosure] Multiple Backdoors found in eEye Products (IRISand SecureIIS), Marc Maiffret |
|---|---|
| Next by Date: | [Full-Disclosure] Trivial Bug in Symantec Security Products, J. Oquendo |
| Previous by Thread: | RE: [Full-Disclosure] Multiple Backdoors found in eEye Products (IRISand SecureIIS), Marc Maiffret |
| Next by Thread: | [Full-Disclosure] Trivial Bug in Symantec Security Products, J. Oquendo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |