public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter•org>
To: Simon Horman <horms@verge•net.au>
Cc: Dan Carpenter <dan.carpenter@oracle•com>,
	Wensong Zhang <wensong@linux-vs•org>,
	Julian Anastasov <ja@ssi•bg>, Patrick McHardy <kaber@trash•net>,
	Jozsef Kadlecsik <kadlec@blackhole•kfki.hu>,
	"David S. Miller" <davem@davemloft•net>,
	netdev@vger•kernel.org, lvs-devel@vger•kernel.org,
	netfilter-devel@vger•kernel.org, netfilter@vger•kernel.org,
	coreteam@netfilter•org, kernel-janitors@vger•kernel.org
Subject: Re: [patch] ipvs: info leak in __ip_vs_get_dest_entries()
Date: Mon, 10 Jun 2013 14:58:22 +0200	[thread overview]
Message-ID: <20130610125822.GA4968@localhost> (raw)
In-Reply-To: <20130610083849.GD1563@verge.net.au>

On Mon, Jun 10, 2013 at 05:38:50PM +0900, Simon Horman wrote:
> On Mon, Jun 03, 2013 at 12:00:49PM +0300, Dan Carpenter wrote:
> > The entry struct has a 2 byte hole after ->port and another 4 byte
> > hole after ->stats.outpkts.  You must have CAP_NET_ADMIN in your
> > namespace to hit this information leak.
> > 
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle•com>
> 
> Signed-off-by: Simon Horman <horms@verge•net.au>
> 
> Pablo, could you take this directly into your tree.

Applied, thanks Simon.

> If possible for v3.10. It also appears to be relevant for stable.

Sure, will do.

      reply	other threads:[~2013-06-10 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  9:00 [patch] ipvs: info leak in __ip_vs_get_dest_entries() Dan Carpenter
2013-06-03 20:00 ` Julian Anastasov
2013-06-04  1:03 ` Simon Horman
2013-06-07  8:33   ` Dan Carpenter
2013-06-10  8:38 ` Simon Horman
2013-06-10 12:58   ` Pablo Neira Ayuso [this message]

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=20130610125822.GA4968@localhost \
    --to=pablo@netfilter$(echo .)org \
    --cc=coreteam@netfilter$(echo .)org \
    --cc=dan.carpenter@oracle$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=horms@verge$(echo .)net.au \
    --cc=ja@ssi$(echo .)bg \
    --cc=kaber@trash$(echo .)net \
    --cc=kadlec@blackhole$(echo .)kfki.hu \
    --cc=kernel-janitors@vger$(echo .)kernel.org \
    --cc=lvs-devel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=netfilter-devel@vger$(echo .)kernel.org \
    --cc=netfilter@vger$(echo .)kernel.org \
    --cc=wensong@linux-vs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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