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/18043] buffer-overflow (read past the end) in wordexp/parse_dollars/parse_param Date: Fri, 06 Mar 2015 17:14:00 -0000 [thread overview] Message-ID: <bug-18043-131-6pzxeIyTrA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18043-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18043 --- 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 895c30cb003857b52c1675f9078e6a799b231bcb (commit) from 5df56c7e3a236b39b3395e042015b541172f652b (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=895c30cb003857b52c1675f9078e6a799b231bcb commit 895c30cb003857b52c1675f9078e6a799b231bcb Author: Paul Pluzhnikov <ppluzhnikov@google.com> Date: Fri Mar 6 09:13:16 2015 -0800 Fix BZ #18043: buffer-overflow (read past the end) in wordexp/parse_dollars/parse_param ----------------------------------------------------------------------- Summary of changes: ChangeLog | 6 ++++++ NEWS | 2 +- posix/wordexp-test.c | 31 +++++++++++++++++++++++++++++++ posix/wordexp.c | 2 +- 4 files changed, 39 insertions(+), 2 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-06 17:14 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-26 23:10 [Bug libc/18043] New: " konstantin.s.serebryany at gmail dot com 2015-02-28 3:49 ` [Bug libc/18043] " ppluzhnikov at google dot com 2015-03-06 17:14 ` cvs-commit at gcc dot gnu.org [this message] 2015-03-06 17:16 ` ppluzhnikov at google dot com 2015-03-09 4:39 ` cvs-commit at gcc dot gnu.org 2015-03-09 6:21 ` konstantin.s.serebryany at gmail dot com 2015-03-09 14:25 ` cvs-commit at gcc dot gnu.org 2015-03-09 14:28 ` ppluzhnikov at google dot com 2015-03-09 16:42 ` konstantin.s.serebryany at gmail dot com 2015-03-09 17:55 ` konstantin.s.serebryany at gmail dot com 2015-03-09 18:20 ` ppluzhnikov at google dot com 2015-03-09 18:39 ` konstantin.s.serebryany at gmail dot com 2015-03-09 18:47 ` konstantin.s.serebryany at gmail dot com 2015-03-09 18:51 ` ppluzhnikov at google dot com 2015-03-09 19:09 ` konstantin.s.serebryany at gmail dot com 2015-03-09 19:10 ` konstantin.s.serebryany at gmail dot com 2015-03-09 19:22 ` ppluzhnikov at google dot com 2015-03-09 19:28 ` konstantin.s.serebryany at gmail dot com 2015-03-09 22:25 ` ppluzhnikov at google dot com 2015-03-09 22:35 ` konstantin.s.serebryany at gmail dot com 2015-03-09 23:16 ` ppluzhnikov at google dot com 2015-03-11 15:57 ` cvs-commit at gcc dot gnu.org 2015-03-11 16:01 ` ppluzhnikov at google dot com 2015-03-19 14:55 ` fweimer at redhat dot com
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-18043-131-6pzxeIyTrA@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: linkBe 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).