Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Signatures
[Top] [All Lists]

Re: [Snort-sigs] SID 4638

Subject: Re: [Snort-sigs] SID 4638
Date: Fri, 01 Jun 2007 16:10:08 -0500
--On Friday, June 01, 2007 16:00:49 -0500 Paul Schmehl <pauls@utdallas.edu> wrote:

--On Friday, June 01, 2007 22:19:27 +0200 rmkml <rmkml@free.fr> wrote:

and do you have false alert if you add ip_proto:46; on this rules ?

I don't think that's possible, is it? This rule is looking at the data in a packet *not* at the IP header. You would need to sort that out first, and I don't think snort has that ability. Or is the data going to include the protocol somehow? The tenth byte of the IP header would tell you what the protocol is, but I don't think snort has rule syntax that looks at that. (I could definitely be wrong.)

After reviewing the docs, I see that I am definitely wrong. Furthermore, this would probably be an excellent improvement to this rule.


So I assume it would look like this, because you would want to check for the protocol first and reject at the point if it doesn't match, right?

alert ip $EXTERNAL_NET any -> $HOME_NET any (msg:"EXPLOIT RSVP Protocol zero length object DoS attempt"; ip_proto:"46"; content:"|01|"; depth:1; offset:11; byte_test:1,<,4,13; pcre:"/^.{10}[\x14\x15]\x01.{1}[\x00-\x03]/sm"; reference:url,www.frsirt.com/english/advisories/2005/0411; classtype:attempted-dos; sid:4638; rev:3; )

Or would you need to use the hex?

alert ip $EXTERNAL_NET any -> $HOME_NET any (msg:"EXPLOIT RSVP Protocol zero length object DoS attempt"; ip_proto:"|2E|"; content:"|01|"; depth:1; offset:11; byte_test:1,<,4,13; pcre:"/^.{10}[\x14\x15]\x01.{1}[\x00-\x03]/sm"; reference:url,www.frsirt.com/english/advisories/2005/0411; classtype:attempted-dos; sid:4638; rev:3; )

Or I suppose you could do:

alert ip $EXTERNAL_NET any -> $HOME_NET any (msg:"EXPLOIT RSVP Protocol zero length object DoS attempt"; ip_proto:"rsvp"; content:"|01|"; depth:1; offset:11; byte_test:1,<,4,13; pcre:"/^.{10}[\x14\x15]\x01.{1}[\x00-\x03]/sm"; reference:url,www.frsirt.com/english/advisories/2005/0411; classtype:attempted-dos; sid:4638; rev:3; )

--
Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

Attachment: p7sM1D38IvHKO.p7s
Description: S/MIME cryptographic signature

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Snort-sigs mailing list
Snort-sigs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-sigs
<Prev in Thread] Current Thread [Next in Thread>