From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net] netfilter: xt_hashlimit: do not allow empty names
Date: Sun, 28 Jan 2018 22:54:29 +0100 [thread overview]
Message-ID: <20180128215429.GB5906@breakpoint.cc> (raw)
In-Reply-To: <1517162045.3715.78.camel@gmail.com>
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Sun, 2018-01-28 at 07:41 -0800, Eric Dumazet wrote:
> > From: Eric Dumazet <edumazet@google.com>
> >
> > Syzbot reported a WARN() in proc_create_data() [1]
> >
> > Issue here is that xt_hashlimit does not check that user space provided
> > an empty table name.
>
> > Signed-off-by: Eric Dumazet <edumazet@google.com>
> > Reported-by: syzbot <syzkaller@googlegroups.com>
> > ---
> > net/netfilter/xt_hashlimit.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/net/netfilter/xt_hashlimit.c b/net/netfilter/xt_hashlimit.c
> > index 5da8746f7b88ff4c9446f256e542e823a6a561b0..eae732e013df92a364b500645360d4606c283a75 100644
> > --- a/net/netfilter/xt_hashlimit.c
> > +++ b/net/netfilter/xt_hashlimit.c
> > @@ -894,6 +894,8 @@ static int hashlimit_mt_check_common(const struct xt_mtchk_param *par,
> > return -ERANGE;
> > }
> >
> > + if (!name[0])
> > + return -EINVAL;
> > mutex_lock(&hashlimit_mutex);
> > *hinfo = htable_find_get(net, name, par->family);
> > if (*hinfo == NULL) {
>
> I wonder if we should also check if name includes a '/' ?
>
> if (!name[0] || strchr(name, '/'))
> return -EINVAL;
I think there should be a helper for this to reject
- 0 length
- /
- .
- ..
in hashlimit case name is IFNMASIZ so we could even use
dev_valid_name() here.
next prev parent reply other threads:[~2018-01-28 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 15:41 [PATCH net] netfilter: xt_hashlimit: do not allow empty names Eric Dumazet
2018-01-28 17:54 ` Eric Dumazet
2018-01-28 21:54 ` Florian Westphal [this message]
2018-02-02 11:49 ` Pablo Neira Ayuso
2018-02-02 11:55 ` Pablo Neira Ayuso
2018-02-02 11:56 ` Pablo Neira Ayuso
2018-02-02 12:12 ` Jan Engelhardt
2018-02-02 12:17 ` Pablo Neira Ayuso
2018-02-02 16:27 ` Eric Dumazet
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=20180128215429.GB5906@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric.dumazet@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 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).