From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: Defeating NMAP Null scans (and Nessus scans).
Date: Wed, 22 Jun 2005 15:26:33 -0500 [thread overview]
Message-ID: <42B9C979.9080701@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0506221845160.21055@yvahk01.tjqt.qr>
> Does it really? What if there happens to be a null-flags/xmas-flags tcp packet
> in an otherwise well-behaved tcp connection? I'd guess it would match
> ESTABLISHED, even if it has got null flags.
As I understand it it is not possible to have the same packet be part of a null AND xmas scan as they are the exact opposite of each other acting on the SAME flags.
As far as not having the ESTABLISHED or RELATED state allowing the scan packets through you would want to have something like this first, before our stateful rule:
# Drop any XMas scan packets.
iptables -t filter -A FORWARD -i $INet -o $LAN -p tcp --tcp-flags ALL ALL -j DROP
# Drop any Null scan packets.
iptables -t filter -A FORWARD -i $INet -o $LAN -p tcp --tcp-flags ALL NONE -j DROP
# We could put any matches for any other type of scan that we wanted to here too.
# Allow any stateful traffic back in.
iptables -t filter -A FORWARD -i $INet -o $LAN -m state --state ESTABLISHED,RELATED -j ACCEPT
# Allow any normal LAN traffic out.
# Note: We should probably do some validity checking here but we will not for simplicity.
iptables -t filter -A FORWARD -i $LAN -o $INet -j ACCEPT
You would probably want to do a corresponding drop in the INPUT chain too.
next prev parent reply other threads:[~2005-06-22 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 12:28 Defeating NMAP Null scans (and Nessus scans) Jason Ziemba
2005-06-22 12:52 ` Jan Engelhardt
2005-06-22 16:47 ` R. DuFresne
2005-06-22 16:59 ` Jan Engelhardt
2005-06-22 19:26 ` R. DuFresne
2005-06-23 11:07 ` Jan Engelhardt
2005-06-24 15:17 ` R. DuFresne
2005-06-29 19:37 ` Kirk
2005-06-30 9:47 ` Kirk
2005-07-06 19:54 ` curby .
2005-07-07 7:13 ` Jörg Harmuth
2005-07-09 10:30 ` Jan Engelhardt
2005-06-22 20:26 ` Taylor, Grant [this message]
2005-06-22 20:37 ` Alexey Toptygin
2005-06-22 20:47 ` R. DuFresne
2005-06-22 21:18 ` Alexey Toptygin
2005-06-23 11:01 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 21:59 Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42B9C979.9080701@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.