TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
> > I wrote the Asylum backdoor signature (and most backdoor signatures in > > RealSecure, if memory serves me) and this is the behavior of many of > them. > > So you're the one to blame. > Essentially > > The reason the source and destination ports are apparently swapped is > > caused both by how the signature actually detects the backdoor traffic > and > > how the event is reported within the network sensor. > > Lets try to get something clear first. Is Realsecure reporting the source > and destination > ports relative to the connnection or relative to the direction of > individual packets? > This is a very important point. > If Realsecure is trying to display the direction of the connection, then > src and dest ports are not "apparently swapped", they ARE swapped. > RealSecure reports the source and destination of the packet which meets the criteria for an attack, or the packet which completes the data segment which meets the criteria. > > Many of these signatures operate by searching through TCP and UDP traffic > > for so called "banners" announced by backdoor and trojan software. > Naturally, > > this traffic originates from the infected computer and not from the > attackers > > computer. > > No. The traffic is originating from the attacker. The attacker is > initiating > the connection to the trojan port. It is true that the PACKETS carrying the > banner > will originate from the trojan port, but what is important is the direction > of the connection not individual packets. What matters is if the IDS administrator has the ability, from host assessment and IDS logs, to determine which is the attacking host and which is the victim. Ideally, this process could be immediatly short circuited by describing the signature in greater detail within the RealSecure help files. Mea culpa, as they say. > > > This explains why you will see an event, for say "Asylum," which > > will show an originating TCP port of 23432 and not the ephemeral port > most > > likely doled out by the attacker's OS. > > Well there's a problem then. Not with documentation as you say below, but > with > the fact that the signature is too simplistic. Simply searching for > "banner" and > packet source port = 23432 is not enough, the signature needs to keep track > of the direction > of the connection. ie search for "banner" and packet source port = 23432 > AND connection dest port > is 23432. I'm aware of less than a handful of backdoor/trojan servers which validate connecting attackers by their source port number. This is why you can use telnet or netcat to connect to most backdoor servers and issue commands. > > > Ultimately what this means is that the RealSecure help sort of makes > sense > > once you know the above details on how these signatures work. However, it > > certainly could be improved to describe the operation of these signatures > > in greater detail. I will talk with our documentation group about having > > these blurbs improved in a future release of RealSecure. > > Having help that only "sort of" makes sense AFTER extra info is ellicited > is hardly > good enough. > > > I previously replied to Mr. Wangler about his inquiry, but unfortunately > > Cc'd the incorrect address for ISS-Forum. The traffic he was seeing > trigger > > this event was in fact a false positive, caused by an FTP 'PASV' command > > originating from an ephemeral which just happened to be 23432. This > > particular signature searches for a banner of "PAS", among others, which > > saw "PASV" and thought it was seeing backdoor traffic. This false > positive > > will be corrected in XPU 4.1, due out shortly. > > This false positive wouldn't occur if the direction of the traffic were > tracked. That's incorrect, this particular false positive would still have occured if the "direction of the traffic were tracked." The falso positive would still be reported but with the source and destination ports swapped as discussed. > > At least one positive thing came out of this, the fact that there is more > to the signatures than simply the ports used. > > So from what you've said, Realsecure is little more than a management > interface onto of ngrep, or perhaps "snoop | grep". > Well.. these backdoor signatures are the simplest of the simple RealSecure decodes, because that's all you need to do to be reasonably sure you're observing backdoor activity. > I probably shouldn't cloud the issue, but on the topic of simplistic > signatures, > how about these URLs being considered as HTTP_Shells > /shareholdercentre/ > /bb/investorCentre/shareholderMeetings.jsp > /bb/investorCentre/shares.jsp > > my guess would be that the signature simply reads: alert if URL contains > "/sh" > This speaks volumes about Realsecure as a product. > Which version of RealSecure are you observing this on? This signature shouldn't be firing on those URL's because the shell name is followed by an alphanumeric character. > Oliver I hope I have been helpful, Oliver. - --krj -- Keith R. Jarvis ([EMAIL PROTECTED]) http://xforce.iss.net Internet Security Systems, Inc. +1-404-236-2833 (direct) The Power to Protect +1-404-236-2624 (fax)
