From: Thomas Jacob <jacob@internet24.de>
To: netfilter-devel@vger.kernel.org
Subject: Incorrect xt_iprange boundary check for IPv6
Date: Sat, 22 Jan 2011 15:10:31 +0100 [thread overview]
Message-ID: <1295705432-2588-1-git-send-email-jacob@internet24.de> (raw)
Developed for and tested on 2.6.27.57, but applies and compiles
in current mainline as well (haven't tested it there though).
See the following script for a demonstration of the problem:
#!/bin/sh
PREFIX=fc42:4242
LEFTOUT=$PREFIX:0:ffff:ffff:ffff:ffff:ffff
FROM=$PREFIX:1::0
MIDDLE=$PREFIX:1::8000:0:0:0
TILL=$PREFIX:1::ffff:ffff:ffff:ffff
RIGHTOUT=$PREFIX:2::0
SUBNET=$PREFIX:1::/64
SOURCE=fc23:2323::1
CHAIN=iprange_bug
ip6tables -S OUTPUT | fgrep -q -- '-A OUTPUT -j '"$CHAIN" \
&& ip6tables -D OUTPUT -j $CHAIN
ip6tables -F $CHAIN 2>/dev/null
ip6tables -X $CHAIN 2>/dev/null
ip6tables -N $CHAIN
ip6tables -A $CHAIN -p icmpv6 --icmpv6-type echo-request -s $SOURCE -m iprange --dst-range $FROM-$TILL
ip6tables -A $CHAIN -p icmpv6 --icmpv6-type echo-request -s $SOURCE -d $SUBNET -j DROP
ip6tables -I OUTPUT 1 -j $CHAIN
ip addr replace $SOURCE/128 dev lo
ip addr replace $LEFTOUT/128 dev lo
ip addr replace $FROM/128 dev lo
ip addr replace $MIDDLE/128 dev lo
ip addr replace $TILL/128 dev lo
ip addr replace $RIGHTOUT/128 dev lo
for IP in $LEFTOUT $FROM $MIDDLE $TILL $RIGHTOUT
do
ping6 -c 1 -W 1 -q -I $SOURCE $IP | grep ^PING
done
echo
ip6tables -vnL $CHAIN
ip addr del $RIGHTOUT/128 dev lo
ip addr del $TILL/128 dev lo
ip addr del $MIDDLE/128 dev lo
ip addr del $FROM/128 dev lo
ip addr del $LEFTOUT/128 dev lo
ip addr del $SOURCE/128 dev lo
ip6tables -D OUTPUT -j $CHAIN
ip6tables -F $CHAIN
ip6tables -X $CHAIN
next reply other threads:[~2011-01-22 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 14:10 Thomas Jacob [this message]
2011-01-22 14:10 ` [PATCH] Incorrect xt_iprange boundary check for IPv6 Thomas Jacob
2011-01-22 14:53 ` Jan Engelhardt
2011-01-23 13:53 ` Jozsef Kadlecsik
2011-01-24 11:31 ` Thomas Jacob
2011-01-24 12:38 ` 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=1295705432-2588-1-git-send-email-jacob@internet24.de \
--to=jacob@internet24.de \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).