Snort mailing list archives
redworm sanity check
From: John Hally <JHally () epnet com>
Date: Sat, 8 Jun 2002 17:55:55 -0400
Hello, I'm looking over some detects I pulled down from the net, and I see a lot of activity bewteen hosts using a source and destination port of 65535. I know that code red/adore worm opened a back door on this port, but I had thought that it only listened on this port, and not communicated with other infected hosts on the same port. does that make sense? I've been looking at these traces a while, and starting to burn out, I just wanted to get a sanity check. ex: 04/01-08:10:28.570578 [**] High port 65535 udp - possible Red Worm - traffic [**] xxx.xxx.6.49:65535 -> xxx.xxx.152.181:65535 thanks in advance. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
Current thread:
- redworm sanity check John Hally (Jun 08)
- FYI - Possible cause for false positive - ICMP L3retriever Ping Michael Gargiullo (Jun 12)
- Re: FYI - Possible cause for false positive - ICMP L3retriever Ping Chris Green (Jun 13)
- FYI - Possible cause for false positive - ICMP L3retriever Ping Michael Gargiullo (Jun 12)
