public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/9914] possible signed integer overflow in libio/iogetdelim.c
Date: Sun, 30 Oct 2011 05:38:00 -0000 [thread overview]
Message-ID: <bug-9914-131-z8btTV7EPc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9914-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9914
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #8 from Rich Felker <bugdal at aerifal dot cx> 2011-10-30 05:37:52 UTC ---
I think it's going to take someone finding a version of gcc that can make the
optimization, and then publishing an attack that results in memory corruption
and possibly privilege elevation, to break through the brick wall known as
Drepper's ego and get this bug fixed...
--
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:[~2011-10-30 5:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9914-131@http.sourceware.org/bugzilla/>
2011-10-24 15:19 ` bugdal at aerifal dot cx
2011-10-29 20:33 ` drepper.fsp at gmail dot com
2011-10-29 20:44 ` jakub at redhat dot com
2011-10-29 21:17 ` drepper.fsp at gmail dot com
2011-10-29 21:20 ` bugdal at aerifal dot cx
2011-10-29 21:37 ` drepper.fsp at gmail dot com
2011-10-29 22:12 ` ldv at altlinux dot org
2011-10-30 5:38 ` bugdal at aerifal dot cx [this message]
2012-02-21 1:35 ` [Bug stdio/9914] " jsm28 at gcc dot gnu.org
2012-03-17 20:36 ` bugdal at aerifal dot cx
2012-03-18 14:28 ` jsm28 at gcc dot gnu.org
2012-09-04 11:27 ` jsm28 at gcc dot gnu.org
2014-07-01 20:44 ` 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-9914-131-z8btTV7EPc@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).