All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] conntrack: fix nfct_clone with certain attribute data types
Date: Tue, 27 Nov 2012 15:05:09 +0100	[thread overview]
Message-ID: <20121127140509.GA8853@1984> (raw)
In-Reply-To: <1353361195-2345-1-git-send-email-fw@strlen.de>

On Mon, Nov 19, 2012 at 10:39:55PM +0100, Florian Westphal wrote:
> some attributes are pointers to malloc'd objects.  Simply
> copying the pointer results in use-after free
> when the original or the clone is destroyed.
> 
> Also, add test case for cloned objects to ensure that
> ct = nfct_new();
> ct2 = nfct_clone(ct);
> nfct_destroy(ct);
> nfct_destroy(ct2);
> 
> won't crash due to double-frees.
> 
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
>  When working on the connlabel stuff I noticed that nfct_clone does a
>  plain memcpy.  Afaics nfct_clone has returned a shallow copy for ages.
>  But documentation implies that it really should do a deep copy.
> 
>  Pablo, could you please double-check?  Thanks!
> 
>  qa/test_api.c       |    6 ++++++
>  src/conntrack/api.c |    2 +-
>  2 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/qa/test_api.c b/qa/test_api.c
> index d5f95e9..fa325c8 100644
> --- a/qa/test_api.c
> +++ b/qa/test_api.c
> @@ -2,6 +2,7 @@
>   * Run this after adding a new attribute to the nf_conntrack object
>   */
>  
> +#include <assert.h>
>  #include <stdio.h>
>  #include <stdlib.h>
>  #include <unistd.h>
> @@ -199,6 +200,10 @@ int main(void)
>  		eval_sigterm(status);
>  	}
>  
> +	ct2 = nfct_clone(ct);
> +	assert(ct2);
> +	nfct_destroy(ct2);
> +
>  	ct2 = nfct_new();
>  	if (!ct2) {
>  		perror("nfct_new");
> @@ -264,6 +269,7 @@ int main(void)
>  	}
>  
>  	nfct_destroy(ct2);
> +	printf("== destroy cloned ct entry ==\n");
>  	nfct_destroy(ct);
>  	nfct_destroy(tmp);
>  	nfexp_destroy(exp);
> diff --git a/src/conntrack/api.c b/src/conntrack/api.c
> index 000571f..ebf0d52 100644
> --- a/src/conntrack/api.c
> +++ b/src/conntrack/api.c
> @@ -147,7 +147,7 @@ struct nf_conntrack *nfct_clone(const struct nf_conntrack *ct)
>  
>  	if ((clone = nfct_new()) == NULL)
>  		return NULL;
> -	memcpy(clone, ct, sizeof(*ct));
> +	nfct_copy(clone, ct, NFCT_CP_ALL);

That seems safe to me.

Still I think NFCT_CP_OVERRIDE is faster. I added that flag way after
to improve a bit the copying time.

It will require also to add the connlabel support to it. See
__copy_fast.

I need to check this again but I think we can remove
src/conntrack/copy.c and make NFCT_CP_ALL behave just like
NFCT_CP_OVERRIDE.

  reply	other threads:[~2012-11-27 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 21:39 [PATCH] conntrack: fix nfct_clone with certain attribute data types Florian Westphal
2012-11-27 14:05 ` Pablo Neira Ayuso [this message]
2012-11-27 14:19   ` Florian Westphal

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=20121127140509.GA8853@1984 \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --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 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.