public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/11615] ld.so segfaults when RLD_MAP is 0
Date: Wed, 15 Feb 2012 22:16:00 -0000	[thread overview]
Message-ID: <bug-11615-131-GH8OiNtWfT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11615-131@http.sourceware.org/bugzilla/>

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |SUSPENDED
         AssignedTo|roland at gnu dot org       |unassigned at sourceware
                   |                            |dot org

--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-15 22:04:41 UTC ---
My impression when I looked at another issue relating to ldd and its use of
ld.so was that ld.so is not expected to do anything sensible with broken
binaries or libraries in any mode, as an architecture-independent matter, and
running with them may involve arbitrary code execution (so you mustn't use
ld.so on possibly hostile code).  Maybe we should generically fix this so that
ldd of hostile code is safe, but then you'd also need to allow for arbitrary
values that are not 0 but still involve writing somewhere inappropriate - that
is, somehow check the address for sanity.

-- 
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:[~2012-02-15 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11615-131@http.sourceware.org/bugzilla/>
2012-02-15 22:16 ` jsm28 at gcc dot gnu.org [this message]
2012-02-15 22:41 ` aurelien at aurel32 dot net
2012-02-15 22:56 ` joseph at codesourcery dot com
2013-10-13  5:48 ` neleai at seznam dot cz
2014-06-30 18:03 ` fweimer at redhat dot com
2010-05-20 12:51 [Bug ports/11615] New: " aurelien at aurel32 dot net
2010-05-20 12:52 ` [Bug ports/11615] " aurelien at aurel32 dot net

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-11615-131-GH8OiNtWfT@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).