public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/16618] wscanf allocates too little memory Date: Sun, 01 Feb 2015 20:13:00 -0000 [thread overview] Message-ID: <bug-16618-131-ofawLj7Kjv@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16618-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16618 Paul Pluzhnikov <ppluzhnikov at google dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |ppluzhnikov at google dot com Assignee|unassigned at sourceware dot org |ppluzhnikov at google dot com --- Comment #1 from Paul Pluzhnikov <ppluzhnikov at google dot com> --- Asked for CVE: http://www.openwall.com/lists/oss-security/2015/02/01/8 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-02-01 20:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-21 1:10 [Bug stdio/16618] New: " jsm28 at gcc dot gnu.org 2014-06-13 8:11 ` [Bug stdio/16618] " fweimer at redhat dot com 2015-02-01 20:13 ` ppluzhnikov at google dot com [this message] 2015-02-02 20:57 ` michael.tremer at ipfire dot org 2015-02-04 10:02 ` [Bug stdio/16618] wscanf allocates too little memory (CVE-2015-1472) fweimer at redhat dot com 2015-02-06 5:52 ` cvs-commit at gcc dot gnu.org 2015-02-06 5:53 ` carlos at redhat dot com 2015-02-06 8:20 ` [Bug stdio/16618] wscanf allocates too little memory (CVE-2015-1472, CVE-2015-1473) fweimer at redhat dot com 2015-02-17 7:25 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:06 ` 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 2015-02-26 9:21 ` fweimer at redhat dot com 2015-07-21 3:17 ` vapier at gentoo dot 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-16618-131-ofawLj7Kjv@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).