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] New adobe vulnerability

Subject: Re: [Snort-sigs] New adobe vulnerability
Date: Thu, 19 Aug 2004 22:46:08 -0500
On Thu, 2004-08-19 at 15:17, Joseph Gama wrote:
My rule was posted the same day as this posting and it
has no false positives:

[...]pcre:"/[\w]+\.pdf%00[\w-_\.!~*'"\(\)]+HTTP\/1\.1/Bi";[...]

Does your rule actually fire on the exploit?

If so, question to nnposter, does his rule (using |00|) fire on the
exploit?

I understand that the preprocessor will convert %00 into |00| within
matches using uricontent. But if Josephs rules works too, does that mean
that anything that is matched using pcre has not been run through
http_inspect?

How does the matching occur? All munged by http_inspect first, then
matched by uricontent and pcre? Or first pcre, then munging by
http_inspect, then uricontent?

Who is right and will alert on the exploit (tested)? pcre using %00 or
uricontent using |00| or both?

Regards,
Frank


BTW: I try to stay away from pcre due to the performance impact. Is that
fear unfounded these days (read, with newer versions of Snort)?

Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>