public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jackie.rosen at hushmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/13446] crash in vfprintf with more than 64 format args and format specifiers Date: Sun, 16 Feb 2014 19:42:00 -0000 [thread overview] Message-ID: <bug-13446-131-BrS9rKyXZa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13446-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=13446 Jackie Rosen <jackie.rosen at hushmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jackie.rosen at hushmail dot com --- Comment #9 from Jackie Rosen <jackie.rosen at hushmail dot com> --- *** Bug 260998 has been marked as a duplicate of this bug. *** Seen from the domain http://volichat.com Page where seen: http://volichat.com/adult-chat-rooms Marked for reference. Resolved as fixed @bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-16 19:42 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-29 3:37 [Bug libc/13446] New: " rcoe at wi dot rr.com 2011-11-29 3:39 ` [Bug libc/13446] " rcoe at wi dot rr.com 2011-11-29 8:56 ` aj at suse dot de 2011-11-29 10:39 ` aj at suse dot de 2011-11-29 12:23 ` rcoe at wi dot rr.com 2011-12-05 12:44 ` gnu at pontohonk dot de 2011-12-18 2:29 ` drepper.fsp at gmail dot com 2011-12-18 6:33 ` aj at suse dot de 2011-12-18 9:11 ` schwab@linux-m68k.org 2014-02-16 19:42 ` jackie.rosen at hushmail dot com [this message] 2014-05-28 19:40 ` schwab at sourceware dot org 2014-06-14 22:31 ` vapier at gentoo dot org 2014-06-14 22:35 ` vapier at gentoo dot org 2014-06-16 12:20 ` [Bug libc/13446] crash in vfprintf with more than 64 format args and format specifiers (CVE-2012-3405) 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-13446-131-BrS9rKyXZa@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).