On Fri, 2016-10-21 at 15:24 +0200, Mark Wielaard wrote:
Bad sh_off or sh_size could trigger a bad malloc or read. Sanity
the header values first before trying to malloc a huge buffer or reading
any data that will certainly fail.
I didn't hear back from the original reporter whether this really solved
their problem. But the change does look correct and desirable. So I have
pushed this to master now.