From: Pablo Neira Ayuso <pablo@netfilter.org>
To: gfree.wind@vip.163.com
Cc: kadlec@blackhole.kfki.hu, fw@strlen.de, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] ebtables: arpreply: Add the standard target sanity check
Date: Mon, 15 May 2017 18:56:02 +0200 [thread overview]
Message-ID: <20170515165602.GA4018@salvia> (raw)
In-Reply-To: <1494582250-120912-1-git-send-email-gfree.wind@vip.163.com>
On Fri, May 12, 2017 at 05:44:10PM +0800, gfree.wind@vip.163.com wrote:
> From: Gao Feng <gfree.wind@vip.163.com>
>
> The info->target is from userspace and it would be used directly.
> So we need to add the sanity check to make sure it is a valid standard
> target, although the ebtables tool has already checked it. Kernel need
> to check anything from userspace.
>
> If the target was set as an evil value, it would break the ebtables
> and cause a panic. Because the non-standard target is treated as one
> offset.
>
> Signed-off-by: Gao Feng <gfree.wind@vip.163.com>
> ---
> net/bridge/netfilter/ebt_arpreply.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/bridge/netfilter/ebt_arpreply.c b/net/bridge/netfilter/ebt_arpreply.c
> index 5929309..c4886d9 100644
> --- a/net/bridge/netfilter/ebt_arpreply.c
> +++ b/net/bridge/netfilter/ebt_arpreply.c
> @@ -68,6 +68,9 @@ static int ebt_arpreply_tg_check(const struct xt_tgchk_param *par)
> if (e->ethproto != htons(ETH_P_ARP) ||
> e->invflags & EBT_IPROTO)
> return -EINVAL;
> + if (INVALID_TARGET)
Please, add:
static inline bool ebt_invalid_target(int target)
{
return (target < -NUM_STANDARD_TARGETS || target >= 0);
}
and use it in this fix.
So we can get rid of this obscure INVALID_TARGET macro.
Thanks.
next prev parent reply other threads:[~2017-05-15 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 9:44 [PATCH nf] ebtables: arpreply: Add the standard target sanity check gfree.wind
2017-05-15 16:56 ` Pablo Neira Ayuso [this message]
2017-05-15 16:56 ` Pablo Neira Ayuso
2017-05-16 0:27 ` Gao Feng
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=20170515165602.GA4018@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=gfree.wind@vip.163.com \
--cc=kadlec@blackhole.kfki.hu \
--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).