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. |

| Subject: | Re: [Snort-users] Port Negation not working? |
|---|---|
| Date: | Thu, 03 Jan 2008 10:09:39 -0500 |
Paul, Thought of something you could try. Add a pass rule for port 25 for each of the 'ip' rules that are firing on the MIME encoded SMTP traffic, e.g. pass tcp $EXTERNAL_NET any -> $HOME_NET 25 \ (msg:"No alert port 25 - SHELLCODE base64 x86 NOOP"; \ content:"RERERERERERERERERERERERERERERERER"; sid:10000001;) Todd Todd Wease wrote:
Hello Paul, Since the rule is an 'ip' rule, the port is insignificant. Todd Paul Melson wrote:Because of a high number of false positives caused by MIME-encoded file attachments, I have modified most of the shellcode/nop rules on one of our sensors so that they should ignore SMTP traffic. However, I have a handful of rules that still fire on SMTP traffic. Here's one example. Original rule: alert ip $EXTERNAL_NET any -> $HOME_NET any (msg:"SHELLCODE base64 x86 NOOP"; \ content:"RERERERERERERERERERERERERERERERER"; metadata:policy security-ips drop; \ classtype:shellcode-detect; sid:12801; rev:1;) Modified rule: alert ip $EXTERNAL_NET any -> $HOME_NET !25 (msg:"SHELLCODE base64 x86 NOOP"; \ content:"RERERERERERERERERERERERERERERERER"; metadata:policy security-ips drop; \ classtype:shellcode-detect; sid:12801; rev:1;) I still get alerts from the modified rule for SMTP traffic containing the "RERERE..." string. I know that the rule/port syntax has been modified in 2.8 to allow port lists, but according to the manual[1], this syntax should still work for port negation. Am I missing something? Thanks, PaulM [1] http://www.snort.org/docs/snort_htmanuals/htmanual_280/node169.html ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Snort-users] custom ruletype (to mysql DB) is broken in snort 2.8.0.1, Agent Smith |
|---|---|
| Next by Date: | Re: [Snort-users] custom ruletype (to mysql DB) is broken in snort 2.8.0.1, Jason Brvenik |
| Previous by Thread: | Re: [Snort-users] Port Negation not working?, Todd Wease |
| Next by Thread: | [Snort-users] custom ruletype (to mysql DB) is broken in snort 2.8.0.1, Agent Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |