public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug stdio/13656] vfprintf nargs integer overflow Date: Mon, 05 Mar 2012 09:39:00 -0000 [thread overview] Message-ID: <bug-13656-131-KbEk5YTtEu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13656-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13656 Andreas Jaeger <aj at suse dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |glibc_2.14, glibc_2.15 AssignedTo|drepper.fsp at gmail dot |carlos at systemhalted dot |com |org --- Comment #1 from Andreas Jaeger <aj at suse dot de> 2012-03-05 09:38:00 UTC --- Fixed in git head, this should be backported to all active branches. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-03-05 9:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-02 20:52 [Bug libc/13656] New: " kees at outflux dot net 2012-02-05 13:02 ` [Bug libc/13656] " thoger at redhat dot com 2012-02-21 2:39 ` [Bug stdio/13656] " jsm28 at gcc dot gnu.org 2012-03-05 9:39 ` aj at suse dot de [this message] 2012-03-05 9:57 ` thoger at redhat dot com 2012-03-05 10:10 ` aj at suse dot de 2012-03-06 14:43 ` thoger at redhat dot com 2012-03-09 8:37 ` eggert at gnu dot org 2014-02-16 19:42 ` jackie.rosen at hushmail dot com 2014-05-28 19:41 ` schwab at sourceware dot org 2014-06-27 9:58 ` [Bug stdio/13656] vfprintf nargs integer overflow (CVE-2012-0864) 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-13656-131-KbEk5YTtEu@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).