From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>,
igor@gooddata.com
Subject: Re: [iptables PATCH 1/3] extensions: libebt_among: Fix for false positive match comparison
Date: Mon, 17 Jul 2023 13:07:35 +0200 [thread overview]
Message-ID: <ZLUg97WtqnWR6aqT@calendula> (raw)
In-Reply-To: <20230715125928.18395-2-phil@nwl.cc>
Hi Phil,
On Sat, Jul 15, 2023 at 02:59:26PM +0200, Phil Sutter wrote:
> When comparing matches for equality, trailing data in among match is not
> considered. Therefore two matches with identical pairs count may be
> treated as identical when the pairs actually differ.
By "trailing data", you mean the right-hand side of this?
fe:ed:ba:be:00:01=10.0.0.1
> Matches' parsing callbacks have no access to the xtables_match itself,
> so can't update userspacesize field as needed.
>
> To fix this, extend struct nft_among_data by a hash field to contain a
> DJB hash of the trailing data.
Is this DJB hash use subject to collisions?
Thanks
> Fixes: 26753888720d8 ("nft: bridge: Rudimental among extension support")
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> extensions/libebt_among.c | 1 +
> iptables/nft-bridge.h | 16 ++++++++
> iptables/nft-ruleparse-bridge.c | 2 +
> .../testcases/ebtables/0009-among-lookup_0 | 39 +++++++++++++++++++
> 4 files changed, 58 insertions(+)
> create mode 100755 iptables/tests/shell/testcases/ebtables/0009-among-lookup_0
>
> diff --git a/extensions/libebt_among.c b/extensions/libebt_among.c
> index a80fb80404ee1..c6132f187f5c3 100644
> --- a/extensions/libebt_among.c
> +++ b/extensions/libebt_among.c
> @@ -179,6 +179,7 @@ static int bramong_parse(int c, char **argv, int invert,
> have_ip = nft_among_pairs_have_ip(optarg);
> poff = nft_among_prepare_data(data, dst, cnt, invert, have_ip);
> parse_nft_among_pairs(data->pairs + poff, optarg, cnt, have_ip);
> + nft_among_update_hash(data);
>
> if (c == AMONG_DST_F || c == AMONG_SRC_F) {
> munmap(argv, flen);
> diff --git a/iptables/nft-bridge.h b/iptables/nft-bridge.h
> index eb1b3928b6543..dacdcb58a7895 100644
> --- a/iptables/nft-bridge.h
> +++ b/iptables/nft-bridge.h
> @@ -133,6 +133,7 @@ struct nft_among_data {
> bool inv;
> bool ip;
> } src, dst;
> + uint32_t pairs_hash;
> /* first source, then dest pairs */
> struct nft_among_pair pairs[0];
> };
> @@ -178,4 +179,19 @@ nft_among_insert_pair(struct nft_among_pair *pairs,
> (*pcount)++;
> }
>
> +/* hash pairs using DJB hash */
> +static inline void
> +nft_among_update_hash(struct nft_among_data *data)
> +{
> + int len = (data->src.cnt + data->dst.cnt) *
> + sizeof(struct nft_among_pair);
> + char *p = (char *)data->pairs;
> + uint32_t hash = 5381;
> +
> + while (len > 0)
> + hash = ((hash << 5) + hash) + p[--len];
> +
> + data->pairs_hash = hash;
> +}
> +
> #endif
> diff --git a/iptables/nft-ruleparse-bridge.c b/iptables/nft-ruleparse-bridge.c
> index 50fb92833046a..4e56d85a318c2 100644
> --- a/iptables/nft-ruleparse-bridge.c
> +++ b/iptables/nft-ruleparse-bridge.c
> @@ -374,6 +374,8 @@ static void nft_bridge_parse_lookup(struct nft_xt_ctx *ctx,
> if (set_elems_to_among_pairs(among_data->pairs + poff, s, cnt))
> xtables_error(OTHER_PROBLEM,
> "ebtables among pair parsing failed");
> +
> + nft_among_update_hash(among_data);
> }
>
> static void parse_watcher(void *object, struct ebt_match **match_list,
> diff --git a/iptables/tests/shell/testcases/ebtables/0009-among-lookup_0 b/iptables/tests/shell/testcases/ebtables/0009-among-lookup_0
> new file mode 100755
> index 0000000000000..c2d2497ad9e12
> --- /dev/null
> +++ b/iptables/tests/shell/testcases/ebtables/0009-among-lookup_0
> @@ -0,0 +1,39 @@
> +#!/bin/sh
> +
> +case "$XT_MULTI" in
> +*xtables-nft-multi)
> + ;;
> +*)
> + echo "skip $XT_MULTI"
> + exit 0
> + ;;
> +esac
> +
> +$XT_MULTI ebtables -A FORWARD --among-src fe:ed:ba:be:00:01=10.0.0.1 -j ACCEPT || {
> + echo "sample rule add failed"
> + exit 1
> +}
> +
> +$XT_MULTI ebtables --check FORWARD --among-src fe:ed:ba:be:00:01=10.0.0.1 -j ACCEPT || {
> + echo "--check must find the sample rule"
> + exit 1
> +}
> +
> +$XT_MULTI ebtables --check FORWARD --among-src fe:ed:ba:be:00:01=10.0.0.2 -j ACCEPT && {
> + echo "--check must fail with different payload"
> + exit 1
> +}
> +$XT_MULTI ebtables --check FORWARD --among-src fe:ed:ba:be:00:01 -j ACCEPT && {
> + echo "--check must fail with shorter payload"
> + exit 1
> +}
> +$XT_MULTI ebtables --check FORWARD --among-src fe:ed:ba:be:00:01=10.0.0.1,fe:ed:ba:be:00:02=10.0.0.2 -j ACCEPT && {
> + echo "--check must fail with longer payload"
> + exit 1
> +}
> +$XT_MULTI ebtables -D FORWARD --among-src fe:ed:ba:be:00:01=10.0.0.1 -j ACCEPT || {
> + echo "sample rule deletion failed"
> + exit 1
> +}
> +
> +exit 0
> --
> 2.40.0
>
next prev parent reply other threads:[~2023-07-17 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 12:59 [iptables PATCH 0/3] Follow-up on dangling set fix Phil Sutter
2023-07-15 12:59 ` [iptables PATCH 1/3] extensions: libebt_among: Fix for false positive match comparison Phil Sutter
2023-07-17 11:07 ` Pablo Neira Ayuso [this message]
2023-07-17 16:23 ` Phil Sutter
2023-07-21 9:59 ` Phil Sutter
2023-07-21 13:56 ` Pablo Neira Ayuso
2023-07-21 14:41 ` Phil Sutter
2023-07-15 12:59 ` [iptables PATCH 2/3] nft: Do not pass nft_rule_ctx to add_nft_among() Phil Sutter
2023-07-15 12:59 ` [iptables PATCH 3/3] nft: Include sets in debug output Phil Sutter
2023-07-28 9:37 ` [iptables PATCH 0/3] Follow-up on dangling set fix Phil Sutter
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=ZLUg97WtqnWR6aqT@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=igor@gooddata.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).