[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150321010043.GR23507@brightrain.aerifal.cx>
Date: Fri, 20 Mar 2015 21:00:43 -0400
From: Rich Felker <dalias@...c.org>
To: Konstantin Serebryany <konstantin.s.serebryany@...il.com>
Cc: musl@...ts.openwall.com
Subject: Re: buffer overflow in regcomp and a way to find more of those
On Fri, Mar 20, 2015 at 05:54:49PM -0700, Konstantin Serebryany wrote:
> >> > > the question is how hard it is to do (1) ?
> >> > >
> >> > > i assume asan is non-trivial to set up for that (or is it
> >> > > enough to replace malloc calls? and some startup logic?)
> >> >
> >> > asan replaces malloc and a few more libc functions.
> >> > It works with various different libcs, so there is a good chance that
> >> > it will work here with no or minimal changes.
> >>
> >> ok i'll try it
> >
> > I would guess it works with no change for static linking, but some
> > changes might be needed for dynamic linking. I'm perfectly happy with
> > all the fuzzing being done with static linking anyway; I don't think
> > dynamic linking would have significant additional code paths whose
> > coverage need checking.
>
> sadly, asan does not support fully static linking.
Is this just an oversight or something fundamental that's hard to fix?
The sort of things it wants to do are much less likely to work with
dynamic linking. Dynamic-linked musl requires all internal symbol
references to be resolved at ld-time and does not support interposing
in front of them.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
