public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rcoe at wi dot rr.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13446] New: crash in vfprintf with more than 64 format args and format specifiers
Date: Tue, 29 Nov 2011 03:37:00 -0000	[thread overview]
Message-ID: <bug-13446-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13446

             Bug #: 13446
           Summary: crash in vfprintf with more than 64 format args and
                    format specifiers
           Product: glibc
           Version: 2.14
               URL: https://bugzilla.novell.com/show_bug.cgi?id=733140
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: rcoe@wi.rr.com
    Classification: Unclassified


Created attachment 6077
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6077
testcase

A user found this in an application that uses format specifiers and
motif was initializing.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff7a91ec8 in _IO_vfprintf_internal (s=<optimized out>,
format=<optimized out>, ap=<optimized out>)
    at vfprintf.c:1739
#2  0x00007ffff7ab5024 in __IO_vsprintf (string=0x603020 "", 
    format=0x601080
"%%P%%S:%s/%%L/%%T/%%N/%%P%%S:%s/%%l_%%t/%%T/%%N/%%P%%S:%s/%%l/%%T/%%N/%%P%%S:%s/%%T/%%N/%%P%%S:%s/%%L/%%T/%%P%%S:%s/%%l_%%t/%%T/%%P%%S:%s/%%l/%%T/%%P%%S:%s/%%T/%%P%%S:%s/%%P%%S:%s/%%L/%%T/%%N/%%P%%S:%"...,
args=0x7fffffffc6c8) at iovsprintf.c:43
#3  0x00007ffff7a9c0a7 in __sprintf (s=<optimized out>, format=<optimized out>)
at sprintf.c:34
#4  0x00000000004009d3 in main (argc=1, argv=0x7fffffffd928) at mtest.c:98

-- 
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.


             reply	other threads:[~2011-11-29  3:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  3:37 rcoe at wi dot rr.com [this message]
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
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@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: 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).