public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17048] posix_spawn_file_actions_addopen fails to copy the path argument
Date: Wed, 11 Jun 2014 21:18:00 -0000	[thread overview]
Message-ID: <bug-17048-131-gYsgRFj184@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17048-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17048

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  89e435f3559c53084498e9baad22172b64429362 (commit)
      from  c3a2ebe1f7541cc35937621e08c28ff88afd0845 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=89e435f3559c53084498e9baad22172b64429362

commit 89e435f3559c53084498e9baad22172b64429362
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Jun 11 23:12:52 2014 +0200

    posix_spawn_file_actions_addopen needs to copy the path argument (BZ 17048)

    POSIX requires that we make a copy, so we allocate a new string
    and free it in posix_spawn_file_actions_destroy.

    Reported by David Reid, Alex Gaynor, and Glyph Lefkowitz.  This bug
    may have security implications.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                     |   13 +++++++++++++
 NEWS                          |    2 +-
 posix/spawn_faction_addopen.c |   13 ++++++++++---
 posix/spawn_faction_destroy.c |   22 ++++++++++++++++++++--
 posix/spawn_int.h             |    2 +-
 posix/tst-spawn.c             |   10 +++++++++-
 6 files changed, 54 insertions(+), 8 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-06-11 21:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 20:19 [Bug libc/17048] New: " alex.gaynor at gmail dot com
2014-06-11 20:21 ` [Bug libc/17048] " alex.gaynor at gmail dot com
2014-06-11 21:18 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-11 21:21 ` fweimer at redhat dot com
2014-06-12 13:53 ` fweimer at redhat dot com
2014-06-12 18:47 ` fweimer at redhat dot com
2014-06-13 13:29 ` [Bug libc/17048] posix_spawn_file_actions_addopen fails to copy the path argument (CVE-2014-4043) fweimer at redhat dot com
2014-06-14 23:32 ` cvs-commit at gcc dot gnu.org
2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org
2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org
2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org
2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org
2015-02-23 15:02 ` cvs-commit at gcc dot gnu.org

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=bug-17048-131-gYsgRFj184@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).