From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] parser_json: only allow concatenations with 2 or more expressions
Date: Wed, 2 Apr 2025 10:44:36 +0200 [thread overview]
Message-ID: <Z-z49Pv9YzdP8zsK@calendula> (raw)
In-Reply-To: <20250402051820.9653-1-fw@strlen.de>
On Wed, Apr 02, 2025 at 07:18:18AM +0200, Florian Westphal wrote:
> The bison grammar enforces this implicitly by grammar rules, e.g.
> "mark . ip saddr" or similar, i.e., ALL concatenation expressions
> consist of at least two elements.
>
> But this doesn't apply to the json frontend which just uses an
> array: it can be empty or only contain one element.
>
> The included reproducer makes the eval stage set the "concatenation" flag
> on the interval set. This prevents the needed conversion code to turn the
> element values into ranges from getting run.
>
> The reproducer asserts with:
> nft: src/intervals.c:786: setelem_to_interval: Assertion `key->etype == EXPR_RANGE_VALUE' failed.
>
> Convert the assertion to BUG() so we can see what element type got passed
> to the set interval code in case we have further issues in this area.
>
> Reject 0-or-1-element concatenations from the json parser.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Reviewed-by: Pablo Neira Ayuso <pablo@netfilter.org>
Thanks
> ---
> src/intervals.c | 4 ++-
> src/parser_json.c | 20 ++++++++------
> .../set_with_single_value_concat_assert | 26 +++++++++++++++++++
> 3 files changed, 41 insertions(+), 9 deletions(-)
> create mode 100644 tests/shell/testcases/bogons/nft-j-f/set_with_single_value_concat_assert
>
> diff --git a/src/intervals.c b/src/intervals.c
> index 71ad210bf759..1ab443bcde87 100644
> --- a/src/intervals.c
> +++ b/src/intervals.c
> @@ -783,7 +783,9 @@ int setelem_to_interval(const struct set *set, struct expr *elem,
> next_key = NULL;
> }
>
> - assert(key->etype == EXPR_RANGE_VALUE);
> + if (key->etype != EXPR_RANGE_VALUE)
> + BUG("key must be RANGE_VALUE, not %s\n", expr_name(key));
> +
> assert(!next_key || next_key->etype == EXPR_RANGE_VALUE);
>
> /* skip end element for adjacents intervals in anonymous sets. */
> diff --git a/src/parser_json.c b/src/parser_json.c
> index 94d09212314f..724cba881623 100644
> --- a/src/parser_json.c
> +++ b/src/parser_json.c
> @@ -1251,6 +1251,16 @@ static struct expr *json_parse_binop_expr(struct json_ctx *ctx,
> return binop_expr_alloc(int_loc, thisop, left, right);
> }
>
> +static struct expr *json_check_concat_expr(struct json_ctx *ctx, struct expr *e)
> +{
> + if (e->size >= 2)
> + return e;
> +
> + json_error(ctx, "Concatenation with %d elements is illegal", e->size);
> + expr_free(e);
> + return NULL;
> +}
> +
> static struct expr *json_parse_concat_expr(struct json_ctx *ctx,
> const char *type, json_t *root)
> {
> @@ -1284,7 +1294,7 @@ static struct expr *json_parse_concat_expr(struct json_ctx *ctx,
> }
> compound_expr_add(expr, tmp);
> }
> - return expr;
> + return expr ? json_check_concat_expr(ctx, expr) : NULL;
> }
>
> static struct expr *json_parse_prefix_expr(struct json_ctx *ctx,
> @@ -1748,13 +1758,7 @@ static struct expr *json_parse_dtype_expr(struct json_ctx *ctx, json_t *root)
> compound_expr_add(expr, i);
> }
>
> - if (list_empty(&expr->expressions)) {
> - json_error(ctx, "Empty concatenation");
> - expr_free(expr);
> - return NULL;
> - }
> -
> - return expr;
> + return json_check_concat_expr(ctx, expr);
> } else if (json_is_object(root)) {
> const char *key;
> json_t *val;
> diff --git a/tests/shell/testcases/bogons/nft-j-f/set_with_single_value_concat_assert b/tests/shell/testcases/bogons/nft-j-f/set_with_single_value_concat_assert
> new file mode 100644
> index 000000000000..c99a26683470
> --- /dev/null
> +++ b/tests/shell/testcases/bogons/nft-j-f/set_with_single_value_concat_assert
> @@ -0,0 +1,26 @@
> +{
> + "nftables": [
> + {
> + "metainfo": {
> + "version": "nftables", "json_schema_version": 1
> + }
> + },
> + {
> + "table": {
> + "family": "ip",
> + "name": "t",
> + "handle": 0
> + }
> + },
> + {
> + "set": {
> + "family": "ip",
> + "name": "s",
> + "table": "t",
> + "type": [ "ifname" ],
> + "flags": [ "interval" ],
> + "elem": [ [] ]
> + }
> + }
> + ]
> +}
> --
> 2.49.0
>
>
prev parent reply other threads:[~2025-04-02 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 5:18 [PATCH nft] parser_json: only allow concatenations with 2 or more expressions Florian Westphal
2025-04-02 8:44 ` Pablo Neira Ayuso [this message]
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=Z-z49Pv9YzdP8zsK@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.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 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.