[Snort-sigs] L3Retriever false positives

Javier Fernandez-Sanguino jfernandez at ...2106...
Tue Jan 25 03:08:03 EST 2005

I believe the L3Retriever information should be enhanced as shown below.

Rule:  alert icmp $EXTERNAL_NET any -> $HOME_NET any (msg:"ICMP 
L3retriever Ping"; icode:0; itype:8; 
reference:arachnids,311; classtype:attempted-recon; sid:466; rev:4;)
Sid:  	 1:466
False positives:
[add] Windows 2000 and Windows XP systems are also known to 
occasionally send similar ICMP echo requests with this content when 
communicating with their domain controller or other Windows systems 
when trying to mount remote shares or doing network discovery.

This has been brought up a number of times in the list:

Message-ID: <C038832A1A43884582CACB4B95217DC2011838EE at ...2548...>
<3D89EF6753768740AE4A1DD594736C0701A80E at ...2587...>
Message-Id: <s0fbae32.096 at ...2651...>
Message-ID: <20040716125316.34288.qmail at ...2644...>

¿Any reason why it's not included yet? I understand that this is 
sometimes seen because HOME_NET and EXTERNAL_NET are not properly 
defined, but for IDS monitoring internal sensors for worm activities 
you really want to have EXTERNAL_NET = HOME_NET so you can detect 
attacks between internal users.

The funny thing is I noticed this while reviewing somebody's Kerio 
Firewall logs which includes this signatures as a "medium priority 
intrusion" (that's probably been fixed in Kerio, he was using an old 
version). Googling I've found people discussing this signature at




More information about the Snort-sigs mailing list