From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Mathias Krause <minipli@googlemail.com>,
Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -mainline] af_key: more info leaks in pfkey messages
Date: Thu, 25 Jul 2013 07:32:06 +0000 [thread overview]
Message-ID: <20130725073205.GQ3109@secunet.com> (raw)
In-Reply-To: <20130724103956.GA30345@elgon.mountain>
On Wed, Jul 24, 2013 at 01:39:57PM +0300, Dan Carpenter wrote:
> This is inspired by a5cc68f3d6 "af_key: fix info leaks in notify
> messages". There are some struct members which don't get initialized
> and could disclose small amounts of private information.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> I'm at the "monkey see, monkey do" level of understanding this code so
> let me know if I've missed something.
>
> diff --git a/net/key/af_key.c b/net/key/af_key.c
> index 456b262..e939d32 100644
> --- a/net/key/af_key.c
> +++ b/net/key/af_key.c
> @@ -2081,6 +2081,7 @@ static int pfkey_xfrm_policy2msg(struct sk_buff *skb, const struct xfrm_policy *
> pol->sadb_x_policy_type = IPSEC_POLICY_NONE;
> }
> pol->sadb_x_policy_dir = dir+1;
> + pol->sadb_x_policy_reserved = 0;
> pol->sadb_x_policy_id = xp->index;
> pol->sadb_x_policy_priority = xp->priority;
>
> @@ -3137,7 +3138,9 @@ static int pfkey_send_acquire(struct xfrm_state *x, struct xfrm_tmpl *t, struct
> pol->sadb_x_policy_exttype = SADB_X_EXT_POLICY;
> pol->sadb_x_policy_type = IPSEC_POLICY_IPSEC;
> pol->sadb_x_policy_dir = XFRM_POLICY_OUT + 1;
> + pol->sadb_x_policy_reserved = 0;
> pol->sadb_x_policy_id = xp->index;
> + pol->sadb_x_policy_priority = 0;
Userspace seems not to care, but the correct setting would be
pol->sadb_x_policy_priority = xp->priority;
So maybe we should send the right priority to userspace, just for
the case that anyone is interested in it.
WARNING: multiple messages have this Message-ID (diff)
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Mathias Krause <minipli@googlemail.com>,
Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch -mainline] af_key: more info leaks in pfkey messages
Date: Thu, 25 Jul 2013 09:32:06 +0200 [thread overview]
Message-ID: <20130725073205.GQ3109@secunet.com> (raw)
In-Reply-To: <20130724103956.GA30345@elgon.mountain>
On Wed, Jul 24, 2013 at 01:39:57PM +0300, Dan Carpenter wrote:
> This is inspired by a5cc68f3d6 "af_key: fix info leaks in notify
> messages". There are some struct members which don't get initialized
> and could disclose small amounts of private information.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> I'm at the "monkey see, monkey do" level of understanding this code so
> let me know if I've missed something.
>
> diff --git a/net/key/af_key.c b/net/key/af_key.c
> index 456b262..e939d32 100644
> --- a/net/key/af_key.c
> +++ b/net/key/af_key.c
> @@ -2081,6 +2081,7 @@ static int pfkey_xfrm_policy2msg(struct sk_buff *skb, const struct xfrm_policy *
> pol->sadb_x_policy_type = IPSEC_POLICY_NONE;
> }
> pol->sadb_x_policy_dir = dir+1;
> + pol->sadb_x_policy_reserved = 0;
> pol->sadb_x_policy_id = xp->index;
> pol->sadb_x_policy_priority = xp->priority;
>
> @@ -3137,7 +3138,9 @@ static int pfkey_send_acquire(struct xfrm_state *x, struct xfrm_tmpl *t, struct
> pol->sadb_x_policy_exttype = SADB_X_EXT_POLICY;
> pol->sadb_x_policy_type = IPSEC_POLICY_IPSEC;
> pol->sadb_x_policy_dir = XFRM_POLICY_OUT + 1;
> + pol->sadb_x_policy_reserved = 0;
> pol->sadb_x_policy_id = xp->index;
> + pol->sadb_x_policy_priority = 0;
Userspace seems not to care, but the correct setting would be
pol->sadb_x_policy_priority = xp->priority;
So maybe we should send the right priority to userspace, just for
the case that anyone is interested in it.
next prev parent reply other threads:[~2013-07-25 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 10:39 [patch -mainline] af_key: more info leaks in pfkey messages Dan Carpenter
2013-07-24 10:39 ` Dan Carpenter
2013-07-25 7:15 ` Mathias Krause
2013-07-25 7:15 ` Mathias Krause
2013-07-25 7:32 ` Steffen Klassert [this message]
2013-07-25 7:32 ` Steffen Klassert
2013-07-25 8:24 ` Dan Carpenter
2013-07-25 8:24 ` Dan Carpenter
2013-07-28 20:04 ` [patch -mainline v2] " Dan Carpenter
2013-07-28 20:04 ` Dan Carpenter
2013-07-28 20:21 ` David Miller
2013-07-28 20:21 ` David Miller
2013-07-29 9:16 ` Steffen Klassert
2013-07-29 9:16 ` Steffen Klassert
2013-07-30 23:26 ` David Miller
2013-07-30 23:26 ` David Miller
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=20130725073205.GQ3109@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.