public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Patsy Griffin <patsy@redhat.com>
To: libc-stable@sourceware.org
Subject: [2.29 COMMITTED] Fix use-after-free in glob when expanding ~user (bug 25414)
Date: Tue, 17 Mar 2020 22:38:14 -0400	[thread overview]
Message-ID: <CAOraFgAWgxTk6M5nh5nUQdRr1S1K8qK1pvx-8KDjt7Hg=yohGQ@mail.gmail.com> (raw)

From: Andreas Schwab <schwab@suse.de>

The value of `end_name' points into the value of `dirname', thus don't
deallocate the latter before the last use of the former.

(cherry picked from commit ddc650e9b3dc916eab417ce9f79e67337b05035c)
---
 posix/glob.c | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/posix/glob.c b/posix/glob.c
index e73e35c510..c6cbd0eb43 100644
--- a/posix/glob.c
+++ b/posix/glob.c
@@ -827,31 +827,32 @@ __glob (const char *pattern, int flags, int
(*errfunc) (const char *, int),
       {
  size_t home_len = strlen (p->pw_dir);
  size_t rest_len = end_name == NULL ? 0 : strlen (end_name);
- char *d;
+ char *d, *newp;
+ bool use_alloca = glob_use_alloca (alloca_used,
+   home_len + rest_len + 1);

- if (__glibc_unlikely (malloc_dirname))
-  free (dirname);
- malloc_dirname = 0;
-
- if (glob_use_alloca (alloca_used, home_len + rest_len + 1))
-  dirname = alloca_account (home_len + rest_len + 1,
-    alloca_used);
+ if (use_alloca)
+  newp = alloca_account (home_len + rest_len + 1, alloca_used);
  else
   {
-    dirname = malloc (home_len + rest_len + 1);
-    if (dirname == NULL)
+    newp = malloc (home_len + rest_len + 1);
+    if (newp == NULL)
       {
  scratch_buffer_free (&pwtmpbuf);
  retval = GLOB_NOSPACE;
  goto out;
       }
-    malloc_dirname = 1;
   }
- d = mempcpy (dirname, p->pw_dir, home_len);
+ d = mempcpy (newp, p->pw_dir, home_len);
  if (end_name != NULL)
   d = mempcpy (d, end_name, rest_len);
  *d = '\0';

+ if (__glibc_unlikely (malloc_dirname))
+  free (dirname);
+ dirname = newp;
+ malloc_dirname = !use_alloca;
+
  dirlen = home_len + rest_len;
  dirname_modified = 1;
       }
-- 
2.21.1

                 reply	other threads:[~2020-03-18  2:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAOraFgAWgxTk6M5nh5nUQdRr1S1K8qK1pvx-8KDjt7Hg=yohGQ@mail.gmail.com' \
    --to=patsy@redhat.com \
    --cc=libc-stable@sourceware.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 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).