From: Jakub Jelinek <jakub@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: Gentoo glibc security advisory
Date: Wed, 18 Aug 2004 09:21:00 -0000 [thread overview]
Message-ID: <20040818070409.GQ30497@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <20040818084135.GA6931@suse.de>
On Wed, Aug 18, 2004 at 10:41:35AM +0200, Thorsten Kukuk wrote:
>
> Hi,
>
> Gentoo has issued an advisory:
> http://www.gentoo.org/security/en/glsa/glsa-200408-16.xml
>
> "An attacker can gain the list of symbols a SUID application uses and their
That's true.
> locations
LD_DEBUG=all doesn't give you exact addresses of symbols
(but LD_TRACE_PRELINKING=1 does, maybe we should turn that off for
__libc_enable_secure and missing /etc/suid-debug).
It only tells you which libraries' symbols are used.
> and can then use a trojaned library taking precendence over those
> symbols to gain information
This is wrong. You can't LD_PRELOAD a trojaned library to a suid binary
(unless it is in the standard paths and sgid I think) nor you can
use LD_LIBRARY_PATH to trick it in any way.
> or perform further exploitation."
>
> with the following patch:
>
> http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-libs/glibc/files/glibc-sec-hotfix-20040804.patch?rev=1.1&content-type=text/vnd.viewcvs-markup
BTW,
* Fixes a glibc bug where certain envvars are interpreted
even if UNSECURE_ENVVARS says to drop them
is wrong, they are interpreted on purpose, but with caution if
__libc_enable_secure.
Jakub
prev parent reply other threads:[~2004-08-18 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 8:41 Thorsten Kukuk
2004-08-18 9:21 ` Jakub Jelinek [this message]
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=20040818070409.GQ30497@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=kukuk@suse.de \
--cc=libc-hacker@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).