From: Florian Westphal <fw@strlen.de>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>
Cc: eric.dumazet@gmail.com, pablo@netfilter.org, kaber@trash.net,
kadlec@blackhole.kfki.hu, davem@davemloft.net,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.or,
Zhouyi Zhou <yizhouzhou@ict.ac.cn>
Subject: Re: [PATCH V2] netfilter: h323: avoid potential attack
Date: Thu, 28 Jan 2016 15:29:59 +0100 [thread overview]
Message-ID: <20160128142959.GB30994@breakpoint.cc> (raw)
In-Reply-To: <1453971597-4811-1-git-send-email-zhouzhouyi@gmail.com>
Zhouyi Zhou <zhouzhouyi@gmail.com> wrote:
> Thanks Eric for your review and advice.
>
> I think hackers chould build a malicious h323 packet to overflow
> the pointer p which will panic during the memcpy(addr, p, len)
>
> For example, he may fabricate a very large taddr->ipAddress.ip;
Can you be more specific?
h323_buffer is backend storage for skb_header_pointer, i.e.
this will error out early when we ask for more data than is available in
packet.
I don't understand how this could overflow anything.
Even assuming 64k packet we'd still have enough room in h323_buffer
for an ipv6 address, no? (we skip the l3/l4 header when extracting
packet payload).
next prev parent reply other threads:[~2016-01-28 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:59 [PATCH V2] netfilter: h323: avoid potential attack Zhouyi Zhou
2016-01-28 12:57 ` Eric Dumazet
2016-01-28 13:14 ` Zhouyi Zhou
2016-01-28 14:00 ` Eric Dumazet
2016-01-28 14:07 ` Eric Dumazet
2016-01-28 14:15 ` One Thousand Gnomes
2016-01-28 14:11 ` Sergei Shtylyov
2016-01-28 14:29 ` Florian Westphal [this message]
2016-01-28 15:13 ` Zhouyi Zhou
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=20160128142959.GB30994@breakpoint.cc \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.or \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=yizhouzhou@ict.ac.cn \
--cc=zhouzhouyi@gmail.com \
/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).