unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: fix memory error in notmuch_config_list_value
Date: Mon, 25 Nov 2019 19:21:24 +0200	[thread overview]
Message-ID: <m2h82r98iz.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20191125023734.1235130-1-david@tethera.net>

On Sun, Nov 24 2019, David Bremner wrote:

> The documentation for notmuch_config_list_key warns that that the
> returned value will be destroyed by the next call to
> notmuch_config_list_key, but it neglected to mention that calling
> notmuch_config_list_value would also destroy it (by calling
> notmuch_config_list_key). This is surprising, and caused a use after
> free bug in _setup_user_query_fields (first noticed by an OpenBSD
> porter, so kudos to the OpenBSD malloc implementation).  This change
> fixes that use-after-free bug.
> ---
>  lib/config.cc | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/lib/config.cc b/lib/config.cc
> index da71c16e..2cd8a0b6 100644
> --- a/lib/config.cc
> +++ b/lib/config.cc
> @@ -150,13 +150,17 @@ notmuch_config_list_valid (notmuch_config_list_t *metadata)
>      return true;
>  }
>  
> +static inline char * _key_from_iterator (notmuch_config_list_t *list) {
> +    return talloc_strdup (list, (*list->iterator).c_str () + CONFIG_PREFIX.length ());
> +}
> +
>  const char *
>  notmuch_config_list_key (notmuch_config_list_t *list)
>  {
>      if (list->current_key)
>  	talloc_free (list->current_key);
>  
> -    list->current_key = talloc_strdup (list, (*list->iterator).c_str () + CONFIG_PREFIX.length ());
> +    list->current_key = _key_from_iterator (list);
>  
>      return list->current_key;
>  }
> @@ -166,7 +170,7 @@ notmuch_config_list_value (notmuch_config_list_t *list)
>  {
>      std::string strval;
>      notmuch_status_t status;
> -    const char *key = notmuch_config_list_key (list);
> +    char *key  = _key_from_iterator (list);

2 spaces, otherwise looks good (on paper)

Tomi

>  
>      /* TODO: better error reporting?? */
>      status = _metadata_value (list->notmuch, key, strval);
> @@ -177,6 +181,7 @@ notmuch_config_list_value (notmuch_config_list_t *list)
>  	talloc_free (list->current_val);
>  
>      list->current_val = talloc_strdup (list, strval.c_str ());
> +    talloc_free (key);
>      return list->current_val;
>  }
>  
> -- 
> 2.24.0
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2019-11-25 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25  2:37 [PATCH] lib: fix memory error in notmuch_config_list_value David Bremner
2019-11-25 17:21 ` Tomi Ollila [this message]
2019-12-09 20:31   ` Daniel Kahn Gillmor

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2h82r98iz.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).