From: "Zhouyi Zhou" <yizhouzhou@ict.ac.cn>
To: "Eric Dumazet" <eric.dumazet@gmail.com>
Cc: "Zhouyi Zhou" <zhouzhouyi@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.org
Subject: Re: Re: [PATCH V2] netfilter: h323: avoid potential attack
Date: Thu, 28 Jan 2016 21:14:42 +0800 (GMT+08:00) [thread overview]
Message-ID: <a703ec.53db.152885f2292.Coremail.yizhouzhou@ict.ac.cn> (raw)
In-Reply-To: <1453985821.7627.17.camel@edumazet-glaptop2.roam.corp.google.com>
Thanks Eric for replying
> -----Original Messages-----
> From: "Eric Dumazet" <eric.dumazet@gmail.com>
> Sent Time: Thursday, January 28, 2016
> To: "Zhouyi Zhou" <zhouzhouyi@gmail.com>
> Cc: 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
>
> On Thu, 2016-01-28 at 16:59 +0800, Zhouyi Zhou 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;
> >
> > Signed-off-by: Zhouyi Zhou <yizhouzhou@ict.ac.cn>
> > ---
>
> Except you did not address my feedback about potentially reading not
> initialized memory.
>
> if the frame length was 1000 bytes, then surely accessing memory at
> offset 8000 will either read garbage, or read data from a prior frame
> and leak secrets.
My patch is intend to prevent kernel panic, to prevent reading garbage
or read data from a prior frame and leak secrets, the prototypes of the
get_h2x5_addr functions and the functions that call get_h2x5_addr should
be changed, should we do this?
>
>
>
Cheers
Zhouyi
next parent reply other threads:[~2016-01-28 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453971597-4811-1-git-send-email-zhouzhouyi@gmail.com>
[not found] ` <1453985821.7627.17.camel@edumazet-glaptop2.roam.corp.google.com>
2016-01-28 13:14 ` Zhouyi Zhou [this message]
2016-01-28 14:00 ` Eric Dumazet
2016-01-28 14:07 ` Eric Dumazet
2016-01-28 14:15 ` One Thousand Gnomes
[not found] ` <20160128142959.GB30994@breakpoint.cc>
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=a703ec.53db.152885f2292.Coremail.yizhouzhou@ict.ac.cn \
--to=yizhouzhou@ict.ac.cn \
--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.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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
all inboxes | Powered by JetHome®