This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug ports/11615] ld.so segfaults when RLD_MAP is 0
- From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 15 Feb 2012 22:04:41 +0000
- Subject: [Bug ports/11615] ld.so segfaults when RLD_MAP is 0
- Auto-submitted: auto-generated
- References: <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.