TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------


  Tim,

 I am also having a problem with the ignore list. I just never narrowed it
down to 5 protocols. Thanks Stephen for that insight on that. I have
several protocols not being ignored.

--Chris Mahn



                                                                                      
                    "Stephen                                                          
                    Cooper"               To:     <[EMAIL PROTECTED]>,           
                    <Stephen.Coope        <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>       
                    [EMAIL PROTECTED]>            cc:                                         
                                          bcc:                                        
                    02/07/01 06:07        Subject:     RE: IPUnknownProtocol -        
                    AM                    255(ARP)                                    
                                                                                      
                                                                                      




Hi Tim,

The IGNORE list does not appear to work for more than 5 protocols. I added
a 6th and it clearly isnt ignoring it. My list contains:

2 88 112 103 50

I also tried

2,88,112,103,50

I am using RS 5, service release 1.1.

Any ideas?

>>> "Farley, Tim (ISSAtlanta)" <[EMAIL PROTECTED]> 30/01/01 20:43:38 >>>

TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------


>  I received several hundred of these events yesterday.  Has
>anyone else received any hits like this? I can't quite
>understand it considering that ARP isn't IP and that
>protocol # 255 is reserved. Any help on this would be
>greatly appreciated. Thanks..

There are sort of two things interacting here that are causing a little
confusion.

IPUnknownProtocol reports any protocol other than the most common ones
(ICMP, UDP, TCP) and the ones that you list in its IGNORE parameter (see
the
advanced tab in your policy file for that event).  The reason for this is
some firewalls can be traversed by sending packets with odd protocol types.
Also there are some known vulnerabilities in some VPN boxes which use
things
like GRE or IP-in-IP which are special protocol types.

You are right that 255 is "reserved" in the official protocol list, so it
is
highly unlikely that this is legitimate traffic.  As of version 2.54 Beta
1,
the popular scanning utility NMAP added an option that will scan hosts for
which protocols they support.  (2.54 Beta 7 is the latest).  It's entirely
possible someone is using this tool (or another similar one) with this
feature enabled to scan you.

This NMAP command line would in fact generate one event as you describe for
each IP in the target range:

     nmap -sO -p 255 10.1.1.0/24

Again, this requires nmap 2.54 beta or later for the -sO option to be
available.  Interestingly enough, by default nmap does not hit protocol 255
when it does a -sO, so the -p option is necessary.  This could mean the
source was using this as a supposed "stealthy" scan, or they could be using
a tool other than nmap.

The reason it says "ARP" in the Event Inspector window is a little bit of
RealSecure arcana.  RealSecure's events (in 5.x and earlier versions) are
very IP-centric.  So every event has to have 2 IP addresses and a protocol
type in them (among other things).

Well ARP is technically not an IP protocol, though it is essential to the
operation of IP.  So RealSecure internally marks events that originated
from
ARP packets (such as "ARP" and "IPDuplicate") as protocol number 255, and
the Workgroup Manager thus reports them as ARP.  In this case, it is
incorrect in doing so.  So just ignore where it says "ARP" in the event
inspector window.

There is one other possibility.  It is possible that RealSecure is picking
up "garbage" packets that are not legal, and misinterpreting them as
protocol 255 because of junk in the packet.  Some network cards do not pass
packets like this up in promiscuous mode, but some do, so whether this is
possible can vary depending on the network card you have in your sensor.

Hope that helps.

=====================================
Tim Farley
X-Force Researcher
Internet Security Systems

[EMAIL PROTECTED]
(404) 236-2600 / Direct Dial (404) 236-2873 / fax (404) 236-2624
http://www.iss.net

Internet Security Systems - The Power to Protect
=====================================





DISCLAIMER: Any e-mail messages from the Bank for International Settlements
are sent in good faith, but shall not be binding nor construed as
constituting any obligation on the part of the Bank.

CONFIDENTIALITY NOTICE: This e-mail contains confidential information,
which is intended only for the use of the recipient(s) named above. If you
have received this communication in error, please notify the sender
immediately via e-mail and return the entire message. Thank you for your
assistance.






Reply via email to