Re: HTTP based trojansFrom: s.wun (email@example.com)
- Previous message: s.wun: "Re: HTTP based trojans"
- In reply to: AQBARROS@BKB.com.br: "RES: HTTP based trojans"
- Next in thread: Rob Shein: "RE: HTTP based trojans"
- Reply: Rob Shein: "RE: HTTP based trojans"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "s.wun" <firstname.lastname@example.org> To: <AQBARROS@BKB.com.br>, <email@example.com> Date: Thu, 7 Nov 2002 10:13:08 +0800
I think this so-called flow-based IDS is about analyse each end-to-end
connection based on what protocol the connection is using. For example, if
protocol is 6, it should follow standard TCP communication standard,
anything other than that will be regarded as Potential hack. That's why in
http connection, it detected communication is not belong to http, so it
should be able to raise alarm.
One can create this kind of analyse with simple programming, not neccessary
to purchase StealthWatch if we understand the principle of it.
Good question! It's just what I want to know, but it seems that my question
did not raise a discussion.
People has been using HTTP based trojans for some years, but only after the
Sensepost Black Hat presentation about Setiri it has become a major point of
I didn't see nobody sharing ideas about detecting (or even blocking) this
stuff. I can imagine a couple of Snort rules to try to detect it, based on
filenames and paths, like cmd.exe, \winnt, etc, but it would find a lot of
false positives and wouldn´t be effective on cases using SSL. So, perhaps
the point is on HIDS; But how can we detect the abnormal behaviour if the
trojan is getting out through a IE window? Which adverse effects there will
be if we block the use of invisible IE windows?
De: s.wun [mailto:firstname.lastname@example.org]
Enviada em: quarta-feira, 6 de novembro de 2002 0:27
Para: AQBARROS@BKB.com.br; email@example.com
Assunto: Re: HTTP based trojans
What other open-source tool do you use to detect this attack?
> As I saw on the last messages about detecting trojans through flow-based
> analysis, I thought if someone already made anything to detect trojans
> use Internet Explorer controls to communicate with the client, even on
> networks that allow only proxied (even authenticated) http connections.
> anyone try to do such kind of thing?