netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>,
	netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [nf-next PATCH] netfilter: nft_exthdr: Search chunks in SCTP packets only
Date: Fri, 11 Jun 2021 13:56:54 +0200	[thread overview]
Message-ID: <20210611115654.GA6356@salvia> (raw)
In-Reply-To: <20210611102624.GI22614@orbyte.nwl.cc>

On Fri, Jun 11, 2021 at 12:26:24PM +0200, Phil Sutter wrote:
> On Thu, Jun 10, 2021 at 07:43:34PM +0200, Pablo Neira Ayuso wrote:
> > On Thu, Jun 10, 2021 at 04:23:16PM +0200, Phil Sutter wrote:
> > > Since user space does not generate a payload dependency, plain sctp
> > > chunk matches cause searching in non-SCTP packets, too. Avoid this
> > > potential mis-interpretation of packet data by checking pkt->tprot.
> > > 
> > > Fixes: 133dc203d77df ("netfilter: nft_exthdr: Support SCTP chunks")
> > > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > > ---
> > >  net/netfilter/nft_exthdr.c | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/net/netfilter/nft_exthdr.c b/net/netfilter/nft_exthdr.c
> > > index 7f705b5c09de8..1093bb83f8aeb 100644
> > > --- a/net/netfilter/nft_exthdr.c
> > > +++ b/net/netfilter/nft_exthdr.c
> > > @@ -312,6 +312,9 @@ static void nft_exthdr_sctp_eval(const struct nft_expr *expr,
> > >  	const struct sctp_chunkhdr *sch;
> > >  	struct sctp_chunkhdr _sch;
> > >  
> > > +	if (!pkt->tprot_set || pkt->tprot != IPPROTO_SCTP)
> > > +		goto err;
> > 
> > nft_set_pktinfo_unspec() already initializes pkt->tprot to zero.
> > 
> > I think it's safe to simplify this to:
> > 
> > 	if (pkt->tprot != IPPROTO_SCTP)
> 
> Are you sure? Checking the spots that (should) initialize
> tprot/tprot_set, in nft_do_chain_inet() it seems that if state->pf is
> neither NFPROTO_IPV4 nor NFPROTO_IPV6, nft_do_chain() is called without
> prior init. Maybe default case should call nft_set_pktinfo_unspec()?

state->pf in nft_do_chain_inet() can only be either NFPROTO_IPV4 or
NFPROTO_IPV6.

pkt->tprot_set is there to deal with a corner case: IPPROTO_IP (0).
If pkt->tprot_set == true and pkt->tprot == 0, it means: "match on
IPPROTO_IP". For other IPPROTO_*, checking pkt->tprot looks safe to me.

> BTW: The final return call in nft_do_chain_inet_ingress() is dead code,
> right?

You mean the default case of nft_do_chain_inet_ingress()? inet/ingress
is special, it allows you to filter IPv4 and IPv6 traffic only.
Anything else from ingress is accepted (you should filter it via
netdev family).

  reply	other threads:[~2021-06-11 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 14:23 [nf-next PATCH] netfilter: nft_exthdr: Search chunks in SCTP packets only Phil Sutter
2021-06-10 17:43 ` Pablo Neira Ayuso
2021-06-11 10:26   ` Phil Sutter
2021-06-11 11:56     ` Pablo Neira Ayuso [this message]
2021-06-11 12:52       ` Phil Sutter
2021-06-11 14:54         ` Pablo Neira Ayuso

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=20210611115654.GA6356@salvia \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --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).