Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 7 Mar 2011 19:32:59 -0500
From: Steve Grubb <>
Cc: "Dmitry V. Levin" <>
Subject: Re: ldd can execute an app unexpectedly

On Monday, March 07, 2011 07:00:11 pm Dmitry V. Levin wrote:
> On Mon, Mar 07, 2011 at 06:27:05PM -0500, Steve Grubb wrote:
> [...]
> >
> >
> > 
> > Besides telling everyone don't do that. ldd could take the PoV that it
> > should only call runtime linkers in trusted directories like /sbin or
> > /usr/sbin. Or it could simply detect that another linker was requested
> > and make you add a "--force" so that you are fully aware that you just
> > let another linker run. (The suggested patch can certainly be improved.
> > But its here just in case you want it.)
> In June of 2002, I suggested to change ldd to avoid invoking programs
> directly, even when it seems like that would work, and invoke the dynamic
> linker as a program instead.
> This change was implemented at least in Owl and ALT Linux:
> bc-2.3.6-owl-alt-ldd.diff
> 7027d2950e9508a434475e04c3af864d169

To be clear, I in no way want credit for this. Its been known for a long time. But if 
requirements have been loosened for CVEs, this is something people want to know about 
and probably patch. I strongly believe that it should be fixed.

Any other skeletons in the closet that never got a CVE?


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.